Saturday, February 24, 2007

What are you most chuffed about getting fixed/working/added?

 To be honest most of my contribution to this release has been in the manager role, most of the code changes were from David and 3rd party contributors.

I guess the thing I'm most jazzed about in the release of this new client that I pushed for would be the CPU feature detection stuff the community has been wanting for a long time. Along with that the client makes an attempt to detect which video card the machine is using.

It has been a 'chicken and the egg' problem, it wasn't something any of the projects were specifically looking for and therefore kept being dropped from the list. Of course the major problem with that is we didn't have any firm numbers on what percentage of the base of machines could handle the more advanced instruction sets.

Now that the information is part of the host record, I'm hoping the stat sites can build some fancy graphics and charts which might encourage one or more of the projects to create a client with specialized instruction sets.

We'll need to improve the server-side scheduler to handle scheduling specialized clients, but in the end I think it'll benefit everyone. Undoubtedly this is going to cause some angst amongst those who are only in it for the credits, as the credit granting gap between a stock client and an optimized client is going to shrink further.

How is boinc going to get around the problem on Windows VISTA where you are not suppose to (and often cannot) write to the 'program files' directory?

We'll be breaking apart the data from the executables using the SHGetFolderPath API. Although we'll need to put a possible override registry value for those who want to store the data on a different drive.

Right now I've been brainstorming on the various upgrade scenario's. ( XP to Vista and  32-bit to 64-bit )

It is a messy problem.

 

To submit questions for next week just click on the comments link below and submit your question.

Thanks in advance.

----- Rom

From this article:
http://www.heise-security.co.uk/news/85807/from/rss09

What the heck, it is bad enough I have to allocate as many resources as I have to avoid being inundated with spam in both email (6000+ a month) and blog (2500+ a month), but now something I've helped to build is being abused.

I guess the criminal element of the world just is not content with crapping in their yard, they have to crap in everyone else's too, even when there isn't any money involved.

I had heard about this early last week, Carl came up with a clever solution for CPDN. Hopefully this won't be all that common.

----- Rom

Monday, February 19, 2007

Is it possible to include a (empty) "skins" folder in the next release?

Sure.

Seems that SETI@Home is a victim of its own success; or maybe a run-away train. Has there been any discussion on methods to allocate resources between projects? For example, implementing a per user work unit limit based on the users contributions to the project; contributions such as money, time, other projects in which user participates.

The philisophy of the BOINC the framework is to let the participants decide how they want to volunteer their resources.  To that end, it is up to each project to sell their project to the community.  Donating computation time to a project is already an expensive proposition, it costs time, electrictity, and internet bandwidth.  To be honest I cannot see a project being successfull if they started selling workunits to process.  At that point I think a project would loose it's fun and cool factors and would find it's big iron contributors defecting to other projects.  Eventually that project would only be left wth the die hard fans wth money to burn and those who were not affected by the cap.

At that point the project is pretty much on life support, and waiting for the people who are funding the project to pull the plug.

What's the development progress in getting the boinc code (I assume 5.9.x now) up to scratch to use wxWidgets 2.8?

Charlie started the port to 2.8, there are a few things on my plate to tackle. Text gets clipped in the wizard for instance. We'll have it up to spec when we start the 5.9-5.10 release push.

Can auto update (I see it in the code for 5.9.x) be turned on in 5.8.8+ or has it been left out?

I'm not sure what the client will do at this point if it receives the auto update tag, it should just be ignored at this point. That feature has another month of work or more before it is ready for use.

What do you think are the major improvement in 5.8.8+ over 5.4.9/11?

There have been so many under the cover improments, I think the big ones are the improved CPU scheduler, the improved work fetech policy, and CPU throttling.  On the Mac we have the sand boxed environment which is a huge improvement.

What are you most chuffed about getting fixed/working/added?

What do you mean by chuffed?

 

To submit questions for next week just click on the comments link below and submit your question.

Thanks in advance.

----- Rom

Saturday, February 10, 2007

Matt B. informed me that GridRepublic has been named a finalist for the Web Awards at the SXSW Interactive Festival. This will be some great PR for BOINC and BOINC based projects.

For further details on how to help out you can go to these websites:

http://gridrepublic.org/

https://secure.sxsw.com/peoples_choice/

 

Apparently you can vote once per day through March 2nd.

 

Good Luck to GridRepublic!!!!!!

 

----- Rom

We just released 5.8.x, so I’m sure there are a lot of questions out there.

Ask away...

 

----- Rom

Thursday, February 01, 2007

Have you seen this GPU programming kit:
http://www.nvidia.com/object/IO_37226.html
What do you think are the difficulties of GPU programming with this and would some work still need to be done by the CPU like on F@H?

I suspect every project would have to be a hybrid and use both the CPU and GPU. At the end of the day the OS needs to know what is going on, otherwise it would just overwrite whatever work you assigned to the GPU with something else.

To be honest, I haven't studied the S@H or R@H source closely enough to know how easy or hard it would be to port using the various toolkits released by the video card manufacturers.

Hopefully we'll start to see more traction in this area with the release of 5.8, since it has some basic video card detection code in it.

 

----- Rom

BOINC 5.8 has now ready for public release.

Some of the highlights for this release include:

  • Simple GUI (Complements of World Community Grid)
  • Basic CPU identification
  • CPU throttling
  • New CPU scheduler
  • New work fetch policy
  • Improved memory management

We have one outstanding issue with the Linux client at this time. As soon as we have resolved it we'll release it as well.

We would like to thank everyone for their hard work in making this a solid release.

----- Rom