Posts by Rom Walton

or novell network shares

Just so long as you're not still running IPX/SPX?? :-)

IPX/SPX had one huge advantage not shared by NetBIOS over TCP/IP: it's drop-dead simple.

Our "modern" windows networks were born as an IBM product designed for networks around five nodes, and have been continually kluged to make them "scale" to the size of an enterprise. "Browsers" to cut down on broadcasts, "Master Browsers" to cut down on browser traffic, Domain Controllers to layer better security, WINS to map NetBIOS names to IP addresses, then the DNS kluge to replace WINS (and put internal and external resolution into the same pile) and finally Active Directory.

All of that while IPX just worked.

I must say I'm not sure that there is any actual research been done at all anymore. It's not like we see any of it or hear anything about it.

Perhaps they did finish the project when the classic SETI ended and this is just a sceem to get money. I mean, they are sending out those e-mails begging for money, like any spam e-mail company.

@ Rom, We have an error that is affecting this XP64 Client and app. Could You please Help on this?

OzzFan,

I've downloaded and installed Firefox 2.x and haven't been able to reproduce the problem.

:(

By chance do you have cookies turned off or something like that?

No, cookies aren't turned off. I just tried it with IE6 and it works fine. Must be a problem with FF2, probably a cache problem.

Just to clarify, since my last post wasn't too explanitory, I go to romwnet.org, scroll down to topic "BOINC Simple GUI is in beta", then I click on "Comments". In FF2, I keep getting that error message that I copied and pasted (I'm still getting it as I type this). Works fine in IE6. I'll keep working at it on my end, as it appears to be a problem with my browser.

What does my site do?

I keep getting an error when clicking on "comments" under the "BOINC has been released in beta heading" (paraphrased).

This is what Firefox 2.0 displays:

An error has been encountered while processing the page. We have logged the error condition and are working to correct the problem. We apologize for any inconvenience.

Theme design by Jelle Druyts
Header image by FreeWebPageHeaders

Am I doing something wrong?

On Windows, you are correct. 'Memory leaks' are a big problem with Windows. I usually reboot my Windows boxes about every 3 to 7 days, or when I notice a problem.

I've written a post on this topic as a result of this thread and being asked about it last week. Maybe it'll provide some insight from a different perspective.

BOINC Client: The evils of 'Returning Results Immediately'

Now here are some other numbers you all might be interested in:
On average jocelyn is processing 314 queries per second.
In the last 5 days jocelyn has processed 144.7 million queries.

The amounts of load RRI can generate is non-trivial.

Thanks Rom, it's really useful to have such authoritative input, and I appreciate that you've put in a lot of effort writing it up for the blog.

I've already turned off RRI on the only fast machine I have on my account, and I won't use it on any I may acquire in the future.

But could I ask about slow machines? A machine at 100 RAC would take ~10 days to reach your example of a 20 WU batch report. How is SETI for disk/database space at the moment? Would you prefer us to keep the queries down, or have the responses back to allow purging?

Is there a current, detailed, up-to-date description of the workings of the scheduler available anywhere? Maybe a flow chart? Something written in human-speak and not just source code files?

About 3/4 of the 10Mb is debugging symbols so that when (note not if) something goes wrong the developers can get some information back about exactly where it went wrong and how it went wrong.