|
21)
Message boards :
BOINC Manager :
Feature Request: Date Received
(Message 68491)
Posted 24 Mar 2016 by Cliff Harding Post: The object is not to rely on 3rd-party software when I should be able to see it on the BOINC Manager itself. |
|
22)
Message boards :
BOINC Manager :
Feature Request: Date Received
(Message 68489)
Posted 24 Mar 2016 by Cliff Harding Post: I would like to see an additional column inserted onto the "Task" tab labeled "Date Received" or " Received" displaying the date/time that the work unit was received on the user's machine, similar to the data/time shown for the "Deadline" column. By displaying this column, a user will be able to ascertain that the work units are following the FIFO order of being executed without having to take an extreme length of time to check to properties popup and noting the date/time for each work unit. The new column should have to same properties as the "Deadline" column. |
|
23)
Message boards :
GPUs :
Need help trying to understand what happened on v7 Cuda50 WUs
(Message 55082)
Posted 25 Jul 2014 by Cliff Harding Post: I had started this thread on SETI main n/c forum and it was suggested that I report it over here. It seems to have been a one time thing since the situation has not happened again. http://setiathome.berkeley.edu/forum_thread.php?id=75254 |
|
24)
Message boards :
BOINC client :
Optimization question?
(Message 54694)
Posted 2 Jul 2014 by Cliff Harding Post: The usage of HDD or SSD is "transparent" for BOINC. For every programm on the computer an SSD is just a faster version of an HDD (the program doesn't care). There is no optimisation by the program needed (and possible). The real optimisiations happen in the fast memory on a computer (RAM, L2-Cache) that's where optimised apps come into play. Here's another question -- Which is the dominate factor L2-Cache or RAM and what is the determining factor in how much RAM is utilized? I have 8GB of RAM but, the most I've seen used in most SETI applications is 75MB. When an AVX app is running it can peak to approx. 151Mb. Total system usage of RAM is approx. 2.5GB peaking at 3, leaving at approx. 5GB free doing nothing. I have 5 WUs running at the moment using a total of approx. 219MB. BOINC Manager is using approx. 57.1. What is the possibility of increasing the limit of RAM being used? Even in the native code apps that will be an improvement. I've noticed that on the 'Disk Usage and Memory' tab of the Computing Preferences' panel, I've indicated 95% usage of the page/swap file, but the file is seldom if ever used even though there's approx. 2GB currently allocated, and I can't tell if BOINC, SETI, or some other application is using it when it is being used. I realize that most of my reasoning concerns SETI, which is my primary project, but I think that it can relate to the manager/client apps as well, based on the constraints/limits of the size of the free RAM. Right now I see approx. 7GB of space (free RAM + page space) not being utilized.. Or should maybe this type of question be addressed by the different projects developers? |
|
25)
Message boards :
BOINC client :
Optimization question?
(Message 54677)
Posted 1 Jul 2014 by Cliff Harding Post: I'm not sure what I'm looking for. As the speed of a CPU & GPU increases WUs take less processing time in their upgraded un-optimized (native code) and their optimized (i.e. Lunatics) states, it would therefore come to the question of how, if possible, to do something about how to use the speed of the SSD in I/O operations. Is it even warranted to even look at the possibility of increasing the speed of I/O operations on SSDs? As an example on my old machine (i7/950, DX58SO, GTX660SC, 6GB, BOINC 7.3.19) AP CPU WUs took approx. 11~13 hrs. to complete and GPU WUs took around 3~5 hrs. using Lunatics 0.41. On my new machine (i7/4770K, ASRock Extreme4, GTX750Ti FTW 8GB, BOINC 7.3.19 -> 7.4.8) these WUs were cut almost in half with the CPU WUs averaging 4~5 hrs. and the GPU around 1~3 hrs. The GTX660SC gave the same results on the new machine. Please note that both machines had/have the same SSD configuration. With my current processing times decreased, imagine what can be accomplished if this thought was possible. |
|
26)
Message boards :
BOINC client :
Optimization question?
(Message 54671)
Posted 1 Jul 2014 by Cliff Harding Post: For BOINC purposes I have a Win7 (x64), 2 x SSD system, with one for the OS which also contains the BOINC system directory/files and the other contains the data directory/files. Since day one BOINC has been running on HDDs and I am presuming that it has been optimized for that medium. With the prevalence of SSDs on the market has any thought been given to the optimization of the manager/client for this medium or does it not make a difference? |
|
27)
Message boards :
BOINC Manager :
BOINC Manager - new projects column
(Message 54611)
Posted 26 Jun 2014 by Cliff Harding Post: @Ageless - Thanks for the info. I hadn't expanded the properties panel enough to notice it. It still would have been nice to see it as a static column on the projects panel. But I guess this will have to do. |
|
28)
Message boards :
BOINC Manager :
BOINC Manager - new projects column
(Message 54602)
Posted 26 Jun 2014 by Cliff Harding Post: I'm new to this board and hopefully something will come of this and it will be passed on to the developers. Currently on the projects page there is a column listing the average work done for all projects listed under an user's account, the value being the amalgamation of all hosts/machines listed for each project. What is the possibility for getting a column inserted showing the average work done for the specific machine that the manager is installed on for each project? Even though both of these values show on the statistics panel in graph form, it would be a good idea to show both values on the project panel as a quick view, saving the user several clicks to get the desired result. |
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.