Large Memory usage in Windows r10 Build

Member Site Forums PyRosetta PyRosetta – General Large Memory usage in Windows r10 Build

  • This topic has 4 replies, 3 voices, and was last updated 10 years ago by Anonymous.
Viewing 2 reply threads
  • Author
    Posts
    • #1976
      Anonymous

        Dear all,

        When running simple scripts such as these, the memory usage of the python interpreter under windows goes to about 5.5 GB. Im using the r10 version of PyRosetta.Is such high memory usage normal?

        Under linux (version ‘56891:56891:6efc58f8abb54611ace5a6cdd7e69e6c970a01ef’) the same script takes about 1 GB.

        Does this perhaps have something to do with the monolith (win) vs namespace (linux) release?

        Best regards,

        Ajasja

         

      • #10268
        Anonymous

          Re monolith vs. namespace memory usage: Monolith build could indeed use a bit more memory, i doubt though that the difference could be that big. Exact difference could be measurement by running only ‘rosetta import’ on monolith build and measuring memory consumption.

          Ajasja, how exactly did you measured memory consumption on windows? 5Gb sounds indeed a bit high. Could it be that it reflect ‘image size’ instead of physically allocated memory?

        • #10289
          Anonymous

            Have you tried both the monolith and namespace builds?

          • #10287
            Anonymous

              The memory usage was measured using process explorer. The working set of the python process running pyrosetta is ~3.7 GB and the virtual size ~5.5 GB.
              Image here http://snag.gy/wIbWx.jpg.
              Below the increase in memory usage when running the simple scripts can be observed.

              The same script uses ~1GB (measured using top) on a mint linux virtual machine.

              PS: Sorry for all the blank posts. I had some “Unexpected errors”

            • #10301
              Anonymous

                I think for windows only monolith build is available.

            Viewing 2 reply threads
            • You must be logged in to reply to this topic.