I apologize for the low limits for this run. We really wanted to get through the run without mork locking up. This, plus we did not start coming off the 90Mbps max until today. There was apparently quite a backlog of demand. In addition, we are still tuning the scheduler on bane.

We will get good compression with the boinc DB reorg tomorrow and I plan to bring the project up with the high limits the next run.
____________

. . . plus we did not start coming off the 90Mbps max until today. There was apparently quite a backlog of demand. In addition, we are still tuning the scheduler on bane . . .

Well, there certainly was quite a backlog of demand, but I think the Cricket graphs may have been pegged for so long (at least in part) because of an unusually heavy flow of AP results going out. That seems to happen with AP's even when we are caught up. The graph flattened out when they ran out.

Having lots of AP's is a good thing for keeping CPU's busy and I love them, but of course they do little to help NVidia GPU's.

Just a thought . . . even a small increase in limits will help get those hungry GPU's through 3 days plus a catchup . . . just as long as that doesn't overly complicate what you're doing on the back end.

Either way, thanks for the update. Even a short word from you or Matt goes a long way toward easing tensions for Type-A's, like me.

Thanks for the updates! The lower limits are kind of a blessing in disguise for me at least, as I have some major host overhauling to do this week. Looks like my cache's will run out right about the time my new parts show up, giving me a chance to get it all reworked and ready for a fresh load on Friday.
____________

When I looked at the cricket graph this morning, I thought, "oh no, mork is hung again". But nope, not this time. It was the UPS supporting our internal file server - the one with all of our home accounts on it. That UPS is now completely dead. We took it out of the loop and everything came up OK. We'll be starting the outage soon.
____________

When I looked at the cricket graph this morning, I thought, "oh no, mork is hung again". But nope, not this time. It was the UPS supporting our internal file server - the one with all of our home accounts on it. That UPS is now completely dead. We took it out of the loop and everything came up OK. We'll be starting the outage soon.

Thanks for the update. But did that internal server failure cause the entire website to fail? Or something else?

When I looked at the cricket graph this morning, I thought, "oh no, mork is hung again". But nope, not this time. It was the UPS supporting our internal file server - the one with all of our home accounts on it. That UPS is now completely dead. We took it out of the loop and everything came up OK. We'll be starting the outage soon.

Before you start the outage, can you please export the stats so that we can all have a good laugh at what BoincStats says is our "best 5 days".

____________I'm only running one computer. Using 2 cores of an old Q8200 CPU for CPU tasks, and 2 cores feeding a single Mid-range GPU, ATI HD7870.
Look at the RAC folks, and ask yourselves why it beats so many multi GPU monster computers :-)

Yeah, well, it's disheartening to watch my computer grind away on SETI calculations, and then never be able to upload the results; there are other projects that I could be working on (though none that I'm more interested in seeing succeed). So I've suspended SETI project calculations until the current problems seem resolved. That will help with the backlog when you start accepting uploads, and allow additional useful (as in, I can upload the results) calculations to be done for other projects.

I mean, look at my stats. It's not like my computer is doing all that much anyway, but, to quote Mr. Scott, "I'm giving her all she's got". I just don't understand why even this minuscule contribution can't get through...
____________

Yeah, well, it's disheartening to watch my computer grind away on SETI calculations, and then never be able to upload the results; there are other projects that I could be working on (though none that I'm more interested in seeing succeed). So I've suspended SETI project calculations until the current problems seem resolved. That will help with the backlog when you start accepting uploads, and allow additional useful (as in, I can upload the results) calculations to be done for other projects.

Do you see a fault in this reasoning?

Yes I do. We are all in the same boat. Nobody can upload results untill they end the outage. I keep crunching untill I run out of work, which is normaly around Thursday night. When they open the gates everyone tries to uplaod. I just let boinc handle that. However i have found a reebot might help unglog the uploads later in the day. Dont get discouraged, some of the power crunchers really have to sweat it out.

Im taking a guess here but did you serve on the USS Ethan Allen? I have worked with a guy who was on a sub.
____________
Old James