University of Maryland Mike P. Cummings  
Center for Bioinformatics and Computational Biology
HomeResearchPublicationsPersonnel

The Lattice Project
About Lattice
Applications
Client Activity
Create Account
Message Boards
Participant Profiles
Questions & Answers
Research Projects
Rules and Policies
Statistics
Teams
Top Computers
Top Participants
Top Teams
Your Account

BOINC Logo



Forum Thread

GARLI 2.1 released
log in

Advanced search

Message boards : News : GARLI 2.1 released

Author Message
Profile Adam Bazinet
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 18 Feb 05
Posts: 1448
Credit: 334,370
RAC: 0
Message 6091 - Posted: 15 Oct 2014, 17:48:35 UTC

I have just released GARLI 2.1 for five platforms (32 and 64 bit Linux, 32 and 64 bit Windows, 64 bit OS X), and have deprecated the 32 bit OS X app version. This version should improve data set load times for large analyses, and may include other improvements that you would notice. Please post if you encounter any problems running the new version.

Roadranner
Send message
Joined: 20 Aug 12
Posts: 1
Credit: 100,018
RAC: 0
Message 6096 - Posted: 17 Oct 2014, 6:40:52 UTC

I get download errors:

237749 The Lattice Project 17.10.2014 08:35:47 [error] Signature verification error for Garli-2.1_windows_x64.exe
237750 The Lattice Project 17.10.2014 08:35:47 [error] Checksum or signature error for Garli-2.1_windows_x64.exe

I resetted the project but it didn't change behaviour.

Whiteknight
Send message
Joined: 15 Jun 12
Posts: 2
Credit: 124,103
RAC: 0
Message 6098 - Posted: 17 Oct 2014, 14:54:48 UTC

Same issue here as well

18/10/2014 3:50:41 a.m. | The Lattice Project | Started download of Garli-2.1_windows_x64.exe
18/10/2014 3:50:46 a.m. | The Lattice Project | Finished download of Garli-2.1_windows_x64.exe
18/10/2014 3:50:46 a.m. | The Lattice Project | [error] Signature verification error for Garli-2.1_windows_x64.exe
18/10/2014 3:50:46 a.m. | The Lattice Project | [error] Checksum or signature error for Garli-2.1_windows_x64.exe

Profile Adam Bazinet
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 18 Feb 05
Posts: 1448
Credit: 334,370
RAC: 0
Message 6099 - Posted: 17 Oct 2014, 15:53:19 UTC

Indeed, there is a problem with code signing that I'm attempting to figure out. The project may be down for maintenance for much of the time I'm working on it. I'll let everyone know when the problem is resolved.

Profile Adam Bazinet
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 18 Feb 05
Posts: 1448
Credit: 334,370
RAC: 0
Message 6102 - Posted: 20 Oct 2014, 18:38:24 UTC

I've generated new keys for the project so in order to process work with the newest versions of the GARLI application, you will have to detach/reattach to the project---I apologize for this inconvenience. Please let me know if you continue to have any trouble with the new GARLI version.

Profile Fox
Avatar
Send message
Joined: 30 Jan 08
Posts: 32
Credit: 1,007,379
RAC: 7
Message 6103 - Posted: 21 Oct 2014, 1:53:48 UTC - in response to Message 6102.

What about WUs currently being crunched? I have 5 going now that have crunched away between 12 and 151 hours each. Will they report okay?

jdzukley
Send message
Joined: 27 May 11
Posts: 66
Credit: 2,353,497
RAC: 492
Message 6104 - Posted: 21 Oct 2014, 15:36:35 UTC

When you detach and reattach you will loose all ongoing work. This morning, I was in the same boat with 2 jobs both at 150+/- hours when one errored out, so I detached and reattached as described below, and lost the remaining 150 task. The good news was that I did all kinds of system maintenance that required reboots, so my main cruncher is up to snuff now.
____________

jdzukley
Send message
Joined: 27 May 11
Posts: 66
Credit: 2,353,497
RAC: 492
Message 6105 - Posted: 21 Oct 2014, 15:39:55 UTC

I just let 3 jobs get downloaded and started. It was interesting to see them commit 15 gegs memory each, so far only each task has only used 1.5 gegs each. I need to watch how this new version works to see how memory is consumed.
____________

Profile Fox
Avatar
Send message
Joined: 30 Jan 08
Posts: 32
Credit: 1,007,379
RAC: 7
Message 6106 - Posted: 21 Oct 2014, 15:56:23 UTC - in response to Message 6104.

When you detach and reattach you will loose all ongoing work. This morning, I was in the same boat with 2 jobs both at 150+/- hours when one errored out, so I detached and reattached as described below, and lost the remaining 150 task.


*nods* I figure once I detach and re-attach I'll lose any current work. The Garli 2.0 WUs were mostly good to me and I still have a handful left that I'd like to finish so I'll keep crunching those until they're all completed or errored out.

Unless that is they won't report successfully even when they are complete because they were using the 'old' Garli. If that's the case I'll just cut my losses now and start using the new ones.

jdzukley
Send message
Joined: 27 May 11
Posts: 66
Credit: 2,353,497
RAC: 492
Message 6107 - Posted: 21 Oct 2014, 17:08:26 UTC
Last modified: 21 Oct 2014, 17:26:01 UTC

Question & Concern: I have now 5 tasks running, each has a commit of 15 gegs or 75 gegs total. Actual memory usage is still low. The first downloaded task has a working memory of 2.4 gegs. Assuming these will be like the older GARLI and each task will take 4+/- gegs I have plenty of total working memory svailable.

However, my total commit memory is at 85% (total computer w/ other apps running). What is likely to happen If I download another GARLI task and the commit goes above 100%? (85 gegs + 15 gegs from a new task....).

I would rather have someone advise me rather of the consequences of over commit rather than to just "experiment". (I know I am mixing %'s and gegs but they are about equal for this discussion).

My values are coming from the windows "Resource Monitor" and the graph for commit is at 85% I understand that I am already over committed verses available memory. Is there a do not exceed point for overcommitting committed memory?
____________

Vitalii Koshura
Send message
Joined: 14 Mar 09
Posts: 8
Credit: 178,579
RAC: 336
Message 6108 - Posted: 21 Oct 2014, 18:53:21 UTC

I have the next message: GARLI needs 17698.00 MB RAM but only 7370.84 MB is available for use.
It really needs 16GB RAM?

jdzukley
Send message
Joined: 27 May 11
Posts: 66
Credit: 2,353,497
RAC: 492
Message 6109 - Posted: 21 Oct 2014, 18:57:28 UTC

I just returned (gone about 1 hour) to find the blue screen of death. On restart, many boinc tasks error out GPUGRID, WCG... The 5 GARLI tasks did not yet checkpoint say 2 hours in...

1 have restarted one, and will monitor the single run for some hours before releasing any further tasks.
____________

John Woods
Send message
Joined: 10 Apr 10
Posts: 2
Credit: 524,368
RAC: 7
Message 6111 - Posted: 21 Oct 2014, 23:35:58 UTC

So far, all of the tasks I've gotten since Sunday have failed with "Error while computing". (That's when I get tasks at all; about half the time I get messages about "GARLI needs 17698.00 MB RAM but only 6144.00 MB is available for use.") I'm running Mac OS X 10.10 ("Yosemite") on an iMac with an Intel Core i7.

Profile Steve Hawker*
Send message
Joined: 30 Oct 12
Posts: 25
Credit: 30,043
RAC: 54
Message 6113 - Posted: 22 Oct 2014, 0:52:02 UTC - in response to Message 6111.

So far, all of the tasks I've gotten since Sunday have failed with "Error while computing". (That's when I get tasks at all; about half the time I get messages about "GARLI needs 17698.00 MB RAM but only 6144.00 MB is available for use.") I'm running Mac OS X 10.10 ("Yosemite") on an iMac with an Intel Core i7.



I checked one of your tasks. You got this in your stderr:

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>

</stderr_txt>
]]>

This is either a memory problem or a code problem. I too have exactly the same error on my MacBook and I run Primegrid without any trouble at all.

Adam, over to you...

boinc127
Send message
Joined: 3 Mar 14
Posts: 7
Credit: 33,176
RAC: 24
Message 6114 - Posted: 22 Oct 2014, 1:03:27 UTC

10.21.2014 19.56.14 | The Lattice Project | Message from server: GARLI needs 17698.00 MB RAM but only 10986.71 MB is available for use.


So are we going back to the 16 GB memory requirement for this project?

Profile Steve Hawker*
Send message
Joined: 30 Oct 12
Posts: 25
Credit: 30,043
RAC: 54
Message 6117 - Posted: 22 Oct 2014, 2:51:21 UTC - in response to Message 6114.

10.21.2014 19.56.14 | The Lattice Project | Message from server: GARLI needs 17698.00 MB RAM but only 10986.71 MB is available for use.


So are we going back to the 16 GB memory requirement for this project?



Who knows? I got this message as well but that didn't stop my machine from downloading and running. Unless that's the underlying problem with all the runtime errors. But as I say, who knows?

Profile Adam Bazinet
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 18 Feb 05
Posts: 1448
Credit: 334,370
RAC: 0
Message 6120 - Posted: 22 Oct 2014, 3:15:44 UTC

There are some recent workunits that require 17000+ MB of RAM. However, I may remove these workunits (at least the ones that have not been picked up yet), as I don't think they'll be feasible to compute for the majority of folks.

boinc127
Send message
Joined: 3 Mar 14
Posts: 7
Credit: 33,176
RAC: 24
Message 6123 - Posted: 22 Oct 2014, 4:55:39 UTC

Who knows? I got this message as well but that didn't stop my machine from downloading and running.


Hats off sir. Thanks for that little bit of information. I checked my swap file setting and had to reset it. I recently did a refresh of Windows 8.1 and I guess the OEM image on this HP computer was built with 4 GB of memory (I guess that's stock) so Windows 8.1 used that 4 GB setting to set up my pagefile. It was only 400 MB when I checked. So I reset it to system managed size and now I can download and crunch Lattice again. I was wondering where all of that extra hard drive space came from!

jdzukley
Send message
Joined: 27 May 11
Posts: 66
Credit: 2,353,497
RAC: 492
Message 6125 - Posted: 22 Oct 2014, 11:20:03 UTC

FYI, I let three jobs run through the night. Each commit was 15 gegs, 45 total, after 8 hours each of the three have taken 7.3 gegs working memory each, 22 gegs total. 8 hours into the run, and are 5.000% complete. The working memory appears to be still being increased. They have yet to checkpoint.
____________

jdzukley
Send message
Joined: 27 May 11
Posts: 66
Credit: 2,353,497
RAC: 492
Message 6127 - Posted: 23 Oct 2014, 3:57:09 UTC

FYI an update on my first limited set of tasks... It looks like they begin to increment from 5% complete after about 22 hours of run time. Working memory is 10.68 gegs, 15.285 gegs are committed. The most currently advanced job is 24.5 hours in and is at 30% complete and progressing rather quickly.

As this is only a few tasks, it may not be representative of all the tasks in the pool.

Bottom line I have to manage - review current memory usage, and know what will be required and either suspend or resume tasks to manage available memory. If anyone would like me to advise how I do this with Windows, advise, and I will post the process I use to do this. Others may also have a better way to do this too. If I do not manage this, BOINC and Garli will allow too much work to commence and that has and will cause my system to crash.
____________


Post to thread

Message boards : News : GARLI 2.1 released

.......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... .......... ..........

University of Maryland     UM Home | Directories | Search | Admissions | Calendar
Copyright © 2016 The Lattice Project
Direct questions and comments to Lattice Admin