Posts by Aaron Finney

21) Message boards : BOINC client : Yet another plea for a 64-bit core client. (Message 6917)
Posted 11 Dec 2006 by Aaron Finney
Post:
Could we get a client that runs natively in XP 64-bit?

too much to ask I know.. but.. alas, there it is.


What's the gain, if the bulk of the DC science projects are in 32?


One less task on the 32-bit emulator.
22) Message boards : BOINC client : Yet another plea for a 64-bit core client. (Message 6814)
Posted 6 Dec 2006 by Aaron Finney
Post:
Could we get a client that runs natively in XP 64-bit?

too much to ask I know.. but.. alas, there it is.
23) Message boards : BOINC client : Are you planning BOINC with GPU support? (Message 6425)
Posted 13 Nov 2006 by Aaron Finney
Post:
My take on this that the GPU's inherent math inaccuracy would tend to limit it to only a few projects.

I know that Dr. Anderson has approached Microsoft a couple of times about porting Boinc to the XBox. When he first approached them a year ago they were not interested. When last contacted in the last couple of months they said they would think about it.


The FLOP accuracy of the x1800 and later GPU's from ATI has been increased exponentially. The 'inherent math inaccuracy' you speak of does not exist on these cards.

Contact this guy over at ATI, he'll help you. Someone should send this info to Dr. Anderson also.

ATI Technologies Inc.
Will Willis
Senior Public Relations Manager
(905) 882-2600, ext. 8293
Email: wwillis@ati.com
For investor relations support, please contact:
ATI Technologies Inc.
Zev Korman, Investor Relations
(905) 882-2600, Ext. 3670
Email: zev@ati.com
High Road Communications
Sarah Vella
(416) 644-2270
Email: svella@highroad.com
Website: www.ati.com
24) Message boards : BOINC client : BOINC not giving correct share of CPU time to each project (Message 4931)
Posted 7 Jul 2006 by Aaron Finney
Post:
Over the last few days, I've been noticing something odd, it's not just einstein WU's, boincsimap's wu's are doing this also. It's making me wonder if it's a problem with the 5.4.9 version of Boinc.
25) Message boards : BOINC client : BOINC not giving correct share of CPU time to each project (Message 4924)
Posted 6 Jul 2006 by Aaron Finney
Post:
There is something wrong with Einstein workunits currently, and I can vouch for the discrephancy.

Einstein WU's are forcing EDF even with very small cache sizes. This really needs to be looked into.
26) Message boards : BOINC Manager : Transfer tab - Percents done (Message 3392)
Posted 8 Mar 2006 by Aaron Finney
Post:
From the checkin notes:

Rom 14 Feb 2006
- Spec Change: Transfers should be 0% until data is actually transfered.


So, any version released after Feb 14th should have this fixed.


Kewl beans. Didn't see that :-D
27) Message boards : BOINC Manager : Transfer tab - Percents done (Message 3386)
Posted 7 Mar 2006 by Aaron Finney
Post:
Transfers that are in queue, (but not yet started) begin at 100%. Once Boincmgr starts the transfer, it resets to 0% then climbs to 100% properly, however - If it is waiting in the queue, the percent complete should not be 100%. If anything, transfers that have not begun yet should read "---" or 0%.

Admittedly, I originally noticed this problem when attaching to Malaria Control.net, but after further review discovered that this anomoly happens when a transfer queue greater than ~2 files is initiated from any project.
28) Message boards : BOINC client : BOINC Applications not giving up CPU Time to cleanmgr.exe (Message 3209)
Posted 23 Feb 2006 by Aaron Finney
Post:
At least Rosetta, Ralph, and LHC are not giving up CPU % to the Drive Cleanup wizard inside Windows XP Home AND PRO.

The cleanmgr.exe uses 97%+ CPU percentage when BOINC activities are suspended (I.E. when Rosetta/ralph/LHC is removed from memory, and suspended) and when it is resumed, the cleanmgr.exe process appears to "hang", and cleanmgr.exe's CPU % drops to <3%.
This MAY be a problem with MS, as it appears to have this problem with every BOINC application I have tested.

This appears to be a problem on at least three of my connected PC's, as I have only tested on the following three so far:

1x Pentium 3.06ghz/533mhz HT Northwood 1024MB ECC 1200Mhz RDRAM Running XP Pro
1x Pentium 3.06ghz/533mhz HT Northwood 512MB ECC 1200Mhz RDRAM Running XP Pro
1x Pentium III 800Mhz w/384MB DDR PC100 RAM Running XP Home

(This message was originally posted inside the Ralph@Home Alpha Test project for Rosetta. It was copied here after it was discovered that it propogates across projects.)
29) Message boards : BOINC Manager : Two computers one account (Message 3155)
Posted 18 Feb 2006 by Aaron Finney
Post:
I have two computers I'd like to have run Boinc. The main one right now is running on 2000 pro, with the newest edition of boinc. The one I'd like to add is running on xp home, with the slighty older version of boinc. I'd like to take the second computer and have it run under the same account as my first computer. How do I do that?

Thanks


Do you currently have them running under different accounts?

If so, detach from the project on the computer you want to change, and then reattach it using the account info on the account you want to add it to.
30) Message boards : BOINC client : Why can't BOINC report results when it completes them? (Message 3150)
Posted 18 Feb 2006 by Aaron Finney
Post:
Since you don't want to read what the solution to your "problem" is, I don't want to read your posts any further. Officially ignored from now on.

And before you ask why it was done this way in Boinc 4.19, that's because it was a bug at that time. Have fun.


Good, cuz you're a freaking idiot. Thank god I don't have to put up with you screwing up my threads anymore!
31) Message boards : BOINC client : Why can't BOINC report results when it completes them? (Message 3148)
Posted 18 Feb 2006 by Aaron Finney
Post:
No, what you are talking about is the fact that you want to report immediately upon uploading. So all the answers we can give you for now is why it isn't done this way.


NO IT ISN'T - READ IT AGAIN.

Then - READ IT AGAIN.

Here, I'll quote the important part.

"47 LHC (or SETI, or rosetta.. etc..) workunits I completed when they are all finished?"

Note, I mention 47 workunits. Not 1. - 47.

Then I say WHEN THEY ARE ALL finished.

If it had read - "47 LHC workunits when each one finishes" or "each LHC workunits when I completed them"

Then I could understand your seemingly oblivious remarks.
32) Message boards : BOINC client : Why can't BOINC report results when it completes them? (Message 3146)
Posted 18 Feb 2006 by Aaron Finney
Post:
Taken from the Wiki:

The reason for the two step policy is that the first stage only has to upload a file to a directory on the Data Server. The second stage requires a connection and contact with the BOINC Database. Because it is easier to report a list of files, the process was divided in this manner so that each part can be performed independently of the other.

If there is a heavy load on the server, if we tried to do both actions within the same transaction, any failure of the process invalidates the entire process. Since the file upload is a very simple transaction it can be easily performed independently of other activities.


Here again we've got some space cadet telling me the reason for the two step process like he didn't read my post. I understand you think you're trying to help, but when you answer with stuff like that it's super fricking infuriating.

Guys.. I don't know how to make it any more clear, this is NOT WHAT I AM TALKING ABOUT.

I am completely aware of the two step process. Please go back and read my original post. Yep, It's down there at the bottom - WoW! Read it 3 or 4 times until it sinks in if you have to, I'm not talking about reporting each workunit when it's done. I'm talking about doing the SECOND stage of reporting, at the point in time after the entire batch of workunits have completed, instead of waiting additional time for god knows what, while BOINC queue's up work from AN ENTIRELY SEPERATE PROJECT. I'm not talking about tea time with the queen, I'm not talking about downloading work or changing my preferences, and I'm certainly not talking about reporting each individual workunit seperately. I understand this procedure in depth, and I most certainly don't need to be patronized or ingratiated by such rhetorical responses.
33) Message boards : BOINC client : Why can't BOINC report results when it completes them? (Message 3145)
Posted 18 Feb 2006 by Aaron Finney
Post:
Still, I don't see why this is not a default action. The work has to get reported anyway.. and if the machine has completed an ENTIRE batch of work from one project, what harm is there in reporting it immediately?

I just can't see any harm it would do, and only see benefits. Not to mention, it -seems- like such an easy change considering how it handles this process now anyway.

Because that the way the project developers want it to be.
I reiterate
This is so it can report batches of WU to the scheduler (which is a separate sever than the upload/download servers), and saves on bandwidth for you and the project.


You just answered the question "Why can't it report entirely complete batches of WU to the scheduler?"

with the answer... "This is so it can report batches of WU to the scheduler."

Excuse me if I either assume you 1. Didn't read what I'm talking about. 2. Are trying to confuse the hell out of even yourself. 3. are trying to upset me.
34) Message boards : BOINC client : Why can't BOINC report results when it completes them? (Message 3107)
Posted 16 Feb 2006 by Aaron Finney
Post:
Still, I don't see why this is not a default action. The work has to get reported anyway.. and if the machine has completed an ENTIRE batch of work from one project, what harm is there in reporting it immediately?

I just can't see any harm it would do, and only see benefits. Not to mention, it -seems- like such an easy change considering how it handles this process now anyway.
35) Message boards : BOINC client : Why can't BOINC report results when it completes them? (Message 3006)
Posted 9 Feb 2006 by Aaron Finney
Post:
Well, I understand all that, but Why can't it also report the completed work when it is finished with all of work from one project? Surely project owners want to have their work as soon as it is finished...?
36) Message boards : BOINC client : Why can't BOINC report results when it completes them? (Message 2992)
Posted 9 Feb 2006 by Aaron Finney
Post:
You know..

Why can't BOINC contact the server to report the 47 LHC (or SETI, or rosetta.. etc..) workunits I completed when they are all finished?

Why does it wait several hours before doing so?

Shouldn't the program start attempting to contact the server to report the 47 completed results once they have all completed?
37) Message boards : BOINC Manager : 2 Suggestions for the Statistics tab of BOINCMGR (Message 2608)
Posted 15 Jan 2006 by Aaron Finney
Post:

That something you like better? In different colours as well. Try 5.3.6 to see it for yourself.

(Took them out as images, was a bit too big ;))


Ahhh, yes.. that's EXACTLY what I've been getting at for months.. lol :) That's pretty.

Now all we need is the rank progression graph.

38) Message boards : BOINC Manager : Bug with AMD 64x2 and Cool'n'Quiet (Message 2599)
Posted 14 Jan 2006 by Aaron Finney
Post:

This must be a bug in BOINC. Anybody else seeing this problem ?

paul



Or a bug in cool 'n' quiet more than likely. Shouldn't you expect Cool'n'Quiet to be a little more aware of what's going on?
39) Message boards : BOINC Manager : 2 Suggestions for the Statistics tab of BOINCMGR (Message 2598)
Posted 14 Jan 2006 by Aaron Finney
Post:
OK.. BOINC is statistics driven. This is a no-brainer.

However, as a program creator, one must be extremely careful in what stats to include inside the statistics tab, lest it become bloat.

The following things have come to my attention as things that might have been overlooked.

1. (I've mentioned this before) The graphs are not "geographically sound". It appears that the spacing between contacts to the server is not relative to the amount of time. So, while a centimeter to the right might indicate 1 day at one point, it may indicate 100 days the very next centimeter, and 42 days the next. I find that very VERY VERY few people watch stats by how often their computer contacts the BOINC server. It would be more appropriate to make the points on the graphs space themselves appropriately in accordance with the amount of time in between them. This should be a VERY simple fix.

2. It would be nice to include a button on the left for overall RANK. RAC can fluctuate wildly, and TC only goes up. Pretty boring. Rank, would be a good indicator of how you are performing compared to others without having to show 5000 other stats windows. Perhaps 2 RANK buttons, one for team rank, and one for overall rank. (after all, there are 2 buttons each for RAC, and TC..)
40) Message boards : BOINC Manager : To those that use Macs, or Linux, or OTHER (Message 2597)
Posted 14 Jan 2006 by Aaron Finney
Post:
Actually, I would bet that 75% or more of the questions asked on the boards are from Windows users. The Mac-specific help areas that I monitor are _much_ less active than the Windows ones, probably even slightly less than the % of machines would indicate. And in general, Linux folks are far more knowledgeable about their systems and how to make things work. As far as BOINC itself goes, I run it on both Mac and Windows, and they both seem to be almost identical. Well, I'll take that back - my Windows box has the "can't connect to localhost" problem on startup at times.


Well that's the thing, It's not the ones that really do know what they are doing that annoy me.. I for one, really like linux :)

It's the people that buy a mac or install linux because they are trying to be "trendy" and then expect it to have EVERY BIT as much support as the windows faction, (or can't understand why every piece of software can't work on their OS) yet know absolutely nothing about computers.


Previous 20 · Next 20

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.