as the message says... that client will have some basic features like return_results_immediately...

Note:
It'll be a stock client without any optimizations turned on. (like cpu affinity, double_num_cpus, reset_debs etc etc etc...)

you can decide here:
POLL

feel free to leave a comment.

---

Join BOINC United now!

as the message says... that client will have some basic features like return_results_immediately...

Note:
It'll be a stock client without any optimizations turned on. (like cpu affinity, double_num_cpus, reset_debs etc etc etc...)

you can decide here:
POLL

feel free to leave a comment.

I know a lot would like an App optimised for 64 bit AMD dual core...

---

Official Abuser of Boinc Buttons...
And no good credit hound!

as the message says... that client will have some basic features like return_results_immediately...

Note:
It'll be a stock client without any optimizations turned on. (like cpu affinity, double_num_cpus, reset_debs etc etc etc...)

you can decide here:
POLL

feel free to leave a comment.

No I would not like a stock 64 bit client, but would like an optimised one :-)

---

No I would not like a stock 64 bit client, but would like an optimised one :-)

The client doesn't do any crunching, just managing work flow and as such any optimisations would be so insignificant as to not make it worth bothering with!

However some might argue that 1 clock cycle saved could represent an extra few nanoseconds spent at the pub...

Andy.

---

No I would not like a stock 64 bit client, but would like an optimised one :-)

The client doesn't do any crunching, just managing work flow and as such any optimisations would be so insignificant as to not make it worth bothering with!

However some might argue that 1 clock cycle saved could represent an extra few nanoseconds spent at the pub...

Andy.

It does run the benchmarks from time to time. You could shave off an extra 60 seconds per week :o)


Regards Hans

---

[quote]
No I would not like a stock 64 bit client, but would like an optimised one :-)

The client doesn't do any crunching, just managing work flow and as such any optimisations would be so insignificant as to not make it worth bothering with!

However some might argue that 1 clock cycle saved could represent an extra few nanoseconds spent at the pub...

Andy.

It does run the benchmarks from time to time. You could shave off an extra 60 seconds per week :o)


Regards Hans[/quote

Well if it's not going to make a difference optimized or stock, then ok :-(

---

BOINC client, not science application.

The BOINC client just schedules work -- it does not crunch.

A 64 bit science application would be interesting -- that is where the heavy lifting is done.

---

No I would not like a stock 64 bit client, but would like an optimised one :-)

The client doesn't do any crunching, just managing work flow and as such any optimisations would be so insignificant as to not make it worth bothering with!

However some might argue that 1 clock cycle saved could represent an extra few nanoseconds spent at the pub...

Andy.

It does run the benchmarks from time to time. You could shave off an extra 60 seconds per week :o)


Regards Hans

Hi Hans,

it'll be no optimized towards "benchmark" results.
running benchmarks from time to time is disabled to.. cuz unnecesary.
(and i might add that the benchmarks in native 64 bit mode tend to be outragougs without applying any kind of optimizations at all)

It'll be just a public "stock" 64 bit boinc and boinc manager release of a client capable of doing other things too..(like affinity etc...)

It's able to run 64 bit AND 32 bit seti and all other apps as well !

the choice is yours ... do you want it or not... simple as that!

---

Join BOINC United now!

BOINC client, not science application.

The BOINC client just schedules work -- it does not crunch.

A 64 bit science application would be interesting -- that is where the heavy lifting is done.

It can be added as well IF there are enough people that want an 64 boinc client... CUZ running a 64 bit app and 32 bit client won't work that well....

---

Join BOINC United now!

Yeah I found a 64 bit app worked, But It didn't crunch nearly as fast as the 32bit 1.2 seti app made by the Chicken(Simon).

Remember, this is for the BOINC Client, not the application that Crunch3r is talking about. :-)

---

BOINC client, not science application.

The BOINC client just schedules work -- it does not crunch.

A 64 bit science application would be interesting -- that is where the heavy lifting is done.

It can be added as well IF there are enough people that want an 64 boinc client... CUZ running a 64 bit app and 32 bit client won't work that well....

Well Go for it...If you make it people will come...

---

Official Abuser of Boinc Buttons...
And no good credit hound!

Hi..

I for instance think that it would be great.. Why the h*ll not..

The more 64bit apps that could show up the more convinced people will be towards going true 64bit instead of staying 32 bit..

So i simply vote "Yes" for a 64 bit boinc build...

And i sincerely beg the Seti Community to respect Crunch3rs demands, no one forced him to make compiled exe's back then, he simply did that in a maner of helping our rigs out there to crunch the fastest it can without sacrifying unvalidating results and that was the main goal after all..

And if Crunch3r is so kind to start to co-operate with Simon and the others we soon could have discustingly frikkin optimised clients which probably noone could've imagined was possible..

Go go go and welcome back to offering your humble services once again..

Kind Regards Vyper

---

_________________________________________________________________________
Addicted to SETI crunching!
Founder of GPU Users Group

Hi..

I for instance think that it would be great.. Why the h*ll not..

The more 64bit apps that could show up the more convinced people will be towards going true 64bit instead of staying 32 bit..

So i simply vote "Yes" for a 64 bit boinc build...

And i sincerely beg the Seti Community to respect Crunch3rs demands, no one forced him to make compiled exe's back then, he simply did that in a maner of helping our rigs out there to crunch the fastest it can without sacrifying unvalidating results and that was the main goal after all..

And if Crunch3r is so kind to start to co-operate with Simon and the others we soon could have discustingly frikkin optimised clients which probably noone could've imagined was possible..

Go go go and welcome back to offering your humble services once again..

Kind Regards Vyper

If I could plus you on this post, I would. LOL I agree completely. I see no reason not to compile a 64 bit client.

And as a side note, Crunch3r, its good to see you back here again.

Jeremy

---

Crunch3r, while you're at it, could you possibly put in a field to select port for remote connections?
That way I could use ssh tunnels to remote machines behind firewalls and see the graphs. Thanks to BoincView I can manage machines this way, albeit without being able to see any graphs.

Cheers,
Andy.

---

No I would not like a stock 64 bit client, but would like an optimised one :-)

it'll be no optimized towards "benchmark" results.

You could still optimize the whole Boinc code except the benchmark routines.

Peter

Hi..

I for instance think that it would be great.. Why the h*ll not..

The more 64bit apps that could show up the more convinced people will be towards going true 64bit instead of staying 32 bit..

So i simply vote "Yes" for a 64 bit boinc build...

And i sincerely beg the Seti Community to respect Crunch3rs demands, no one forced him to make compiled exe's back then, he simply did that in a maner of helping our rigs out there to crunch the fastest it can without sacrifying unvalidating results and that was the main goal after all..

And if Crunch3r is so kind to start to co-operate with Simon and the others we soon could have discustingly frikkin optimised clients which probably noone could've imagined was possible..

Go go go and welcome back to offering your humble services once again..

Kind Regards Vyper

I agree and welcome you back.

There got to be a number people out there with 64-bit platforms that would welcome the help.

Yes, I want it.

Torrey Lauer
Modern Travel Services / Rainbow Sky Travel
moderntravel d0.1t net / rainbowskytravel d01.5 com

---

I just looked at the task manager on my Win2K machine, and since I rebooted this morning, BOINC has used 0:00 minutes.

I'm not sure how "faster" would be better.

---

as the message says... that client will have some basic features like return_results_immediately...

Note:
It'll be a stock client without any optimizations turned on. (like cpu affinity, double_num_cpus, reset_debs etc etc etc...)

you can decide here:
POLL

feel free to leave a comment.

SInce 64b apps are going to need BOINCmanager to be 64b, of course we want a 64b BOINCmanager client.

IMHO the most important features besides 64b of such a thing are
default priority
cpu affinity
return results immediately
*some way of guaranteed save to disk of work done so far if/when abnormal exit occurs.
*some way of overlapping IO of new WU's with crunching of more mature WU's given that inital IO to build tables/etc is +much+ slower than computation once those tables are built.

---

(edited)

IMHO the most important features besides 64b of such a thing are
default priority

return results immediately

While crunchers might find this feature "cool" it does add load to the project servers.

---