RALPH@home

Win10 3.71 Unhandled Exception: Reason: Out Of Memory (backrub)

  UW Seal
 
[ Home ] [ Join ] [ About ] [ Participants ] [ Community ] [ Statistics ]
  [ login/out ]


Advanced search

Message boards : RALPH@home bug list : Win10 3.71 Unhandled Exception: Reason: Out Of Memory (backrub)

AuthorMessage
rjs5

Joined: Jul 5 15
Posts: 16
ID: 49321
Credit: 73,354
RAC: 16
Message 6044 - Posted 6 Feb 2016 20:14:48 UTC

    This workload may have been out of its 4gb 32-bit memory space limit but my machine still had 18GB free when this aborted.

    Ralphie is taking dumps on my machine. There are a number on this Win10 machine.
    http://ralph.bakerlab.org/show_host_detail.php?hostid=35400
    started at 2016- 2- 5 23:31:34, and
    took a dump 40 min later. 02/06/16 00:19:17

    Task ID 3733284
    Name 02_2016_3r8b_backrub_design_20294_68_1
    Workunit 3289094

    minirosetta_3.71_windows_x86_64.exe

    http://ralph.bakerlab.org/result.php?resultid=3733284

    Profile [VENETO] boboviz

    Joined: Apr 9 08
    Posts: 508
    ID: 4205
    Credit: 727,228
    RAC: 146
    Message 6045 - Posted 7 Feb 2016 7:54:22 UTC - in response to Message 6044.

      dekim said:

      Yes, I'm running a test of a new type of job that runs small perturbations of the protein backbone and then does a round of design. The design protocol can use a lot of memory. I realize that this will be problematic and will see if we can distribute these jobs to high memory machines.


      It's time to pass to 64 bit native app?? :-)

      rjs5

      Joined: Jul 5 15
      Posts: 16
      ID: 49321
      Credit: 73,354
      RAC: 16
      Message 6046 - Posted 7 Feb 2016 17:05:30 UTC - in response to Message 6045.

        dekim said:
        Yes, I'm running a test of a new type of job that runs small perturbations of the protein backbone and then does a round of design. The design protocol can use a lot of memory. I realize that this will be problematic and will see if we can distribute these jobs to high memory machines.


        It's time to pass to 64 bit native app?? :-)


        I don't think 64-bit needs to be a requirement. I am not sure how much benefit, performance wise, it would offer either. I have guessed 10% or 20% ... I think. I probably should build a couple 32-bit variants and measure results on same hardware and compiler.

        It is just a memory leak or a memory management integration problem with the new program code. 4gb is a lot of memory space. BOINCTASKS says the current Rosetta Windows 32-bit is taking 460mb of memory space. I doubt the new changes mean the memory requirement has gone up 10x.

        If they cannot make Rosetta work in 32-bit, then they will have to look at all the issues that are building pressure to improve their TASK distribution of jobs.

        If they cannot get it to work in 4gb (32-bits):
        - 32-bit machines will not work for that version.
        - 64-bit machines with <small>gb of memory will not work for that version.
        - 64-bit machines with just enough memory PLUS disk paging space will work BUT with <many times> slow down .... complete the same work .... but will burn out the disk head seek mechanism faster ... which I would not run. If my disk light goes on solid, I find out why and stop running the problem program. I just did that with the Linux tracker-miner (I shut down the indexer).


        Trotador

        Joined: May 7 10
        Posts: 19
        ID: 15474
        Credit: 6,653,683
        RAC: 5,484
        Message 6047 - Posted 7 Feb 2016 20:29:26 UTC - in response to Message 6046.

          Quote from thread http://ralph.bakerlab.org/forum_thread.php?id=567

          Trotador
          The current Ralph WUs use huge amounts of RAM, I've seen up to 4 Gb per unit, is it on purpose? any new kind of simulation?

          thanks for the info


          Dekim

          Yes, I'm running a test of a new type of job that runs small perturbations of the protein backbone and then does a round of design. The design protocol can use a lot of memory. I realize that this will be problematic and will see if we can distribute these jobs to high memory machines. We may just not be able to run these on R@h.

          Profile [VENETO] boboviz

          Joined: Apr 9 08
          Posts: 508
          ID: 4205
          Credit: 727,228
          RAC: 146
          Message 6048 - Posted 8 Feb 2016 22:14:59 UTC - in response to Message 6046.

            Last modified: 8 Feb 2016 22:24:07 UTC

            It is just a memory leak or a memory management integration problem with the new program code. 4gb is a lot of memory space. BOINCTASKS says the current Rosetta Windows 32-bit is taking 460mb of memory space. I doubt the new changes mean the memory requirement has gone up 10x.

            If they cannot make Rosetta work in 32-bit, then they will have to look at all the issues that are building pressure to improve their TASK distribution of jobs.


            This is the message on my machine
            08/02/2016 23:11:14 | ralph@home | Rosetta Mini needs 7629.39 MB RAM but only 7356.70 MB is available for use.

            If this will be the future, i need to buy some ram modules :-P

            Message boards : RALPH@home bug list : Win10 3.71 Unhandled Exception: Reason: Out Of Memory (backrub)


            Home | Join | About | Participants | Community | Statistics

            Copyright © 2017 University of Washington

            Last Modified: 20 Nov 2008 19:41:56 UTC
            Back to top ^