I wonder if there is any chance to change the view "style" of credits? I mean - instead of 1234567 to show 1,234,567? it's way better visible :-)
____________

Mark,

And one more thing. Recently I've got problem with RAM and took out 2 of 3 sticks from my rig and also I have to reduce timing from 7-7-7-24 to 9-9-9-30. I made CPU benchmarking and I was really surprised that the values it gives are pretty much the same. But in fact it takes 3h20m for a WU in POEM instead of 2h10m.

So, if there is any chance to make this benchmark more realistic?
____________

Mark,

And one more thing. Recently I've got problem with RAM and took out 2 of 3 sticks from my rig and also I have to reduce timing from 7-7-7-24 to 9-9-9-30. I made CPU benchmarking and I was really surprised that the values it gives are pretty much the same. But in fact it takes 3h20m for a WU in POEM instead of 2h10m.

So, if there is any chance to make this benchmark more realistic?

Thx guys for your answers :-)

So in fact i should not pay too much attention on these values and i should use so-called "usual" benchmarks to estimate how fast my rig is. clear, no question.

There ia another... hmm... request. If there is any chance to make BOINC save WUs before closing? Coz right now it loosing 2-3% of each WU. Yep, I put "30 secs" in web, but the story is there...
____________

Thx guys for your answers :-)

So in fact i should not pay too much attention on these values and i should use so-called "usual" benchmarks to estimate how fast my rig is. clear, no question.

There ia another... hmm... request. If there is any chance to make BOINC save WUs before closing? Coz right now it loosing 2-3% of each WU. Yep, I put "30 secs" in web, but the story is there...

Just a little clarification on the "write to disk" parameter ... it really means "use this as a multiplier per core" ... so setting 90 seconds on an i7 limits disk writing to every 720 seconds. One of the keys here is that if you tell BOINC not to write to disk it keeps stuffing intermediate results into memory, after that the OS takes over and if you don't have enough memory it writes it to the swap file (which is yes, you know it, on your disk) and when it is allowed to flush from memory to disk it ends up reading from the swap file and writing to the real disk location. I mention this for crunchers who are running kind of tight on memory because setting this parameter for too long could actually slow you down.
____________
Thanks - Steve

Depends on BOINC version. From the 6.10.14 change log...

- client: don't multiply checkpoint interval (i.e., "disk interval" pref) by # processors.

- actually, make it "Tasks checkpoint to disk at most every ..." and change it in the advanced prefs dialog too

Paul D. Buck

the idea of such benchmark is to check how hardware changes effects on BOINC. Sure, I can start any other benchmark to check, but the truth is that synthetic results are too far from "real life".

In my understanding it should work like this: it's necessary to have very short "benchmark WUs" for at least major projects and give a choice of these "benchmark WUs" OR check what project this user running and start that WU which suits better.

As advantage of this approach:
- we can test real productivity of the hatdware in terms of real project
- we can test not CPU only but GPU also.

But I'm sure if it's easy or not to program this and where to take these "benchmark WUs" (from the projects?)

Anyway it's just my personal ideas how to make this benchmark real, otherwise (sorry to say) thet are pretty much useless.
____________

the idea of such benchmark is to check how hardware changes effects on BOINC. Sure, I can start any other benchmark to check, but the truth is that synthetic results are too far from "real life".

In my understanding it should work like this: it's necessary to have very short "benchmark WUs" for at least major projects and give a choice of these "benchmark WUs" OR check what project this user running and start that WU which suits better.

the idea of such benchmark is to check how hardware changes effects on BOINC. Sure, I can start any other benchmark to check, but the truth is that synthetic results are too far from "real life".

In my understanding it should work like this: it's necessary to have very short "benchmark WUs" for at least major projects and give a choice of these "benchmark WUs" OR check what project this user running and start that WU which suits better.

Which has long been my assertion. We need to benchmark with actual tasks...

For just as long UCB has been rejecting this concept along with a host of others ...