Hello,

I have used the BOINC client software for many years on many systems. I have had several systems for personal use and employed the win32 and x64 clients.

When a system is in use I prefer to utilize the entire processing power for my tasks.

When the BOINC client is open, everything has a large amount of visible lag (e.g. 920/6gb/275 or p4-1.8/1gb/4mx-64mb systems). I have attempted many different settings in the BOINC preferences without success. However,

When I snooze BOINC, the system does not regain its performance. It is only after the client is exited that it can be operated normally.

Are there any plans to enforce snooze, or minimally create an option to have it function as though BOINC were completely closed?

This problem is responsible for an extreme loss in processing time, due to my failure to (always) reactivate the client when I leave a system.

Ryan Lewis

P.S. An option to configure the duration of snooze or 'Snooze until idle' would be appreciated (when it becomes useful).

When the BOINC client is open, everything has a large amount of visible lag...

It is only after the client is exited that it can be operated normally.

Are you really speaking of the client (boinc) or of the manager (boincmgr)?

The manager is known to use an excessive amount of system resources if there are very many tasks to display (>1000) and it can be exited without stopping the client.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

Sekerob,

Leave Application in Memory was obvious to me. The configuration is 12.5% of memory while the system is in use and the load has never approached the amount of physical memory.

Notable effects of this problem is frame skipping if viewing a video file or a performance drop when playing a game.

The BOINC manager task list has less than ten available.

I appreciate the education, but as you note

[there's a few snags that apparently even through the later 6.10 are not fully worked out].

there are problems with BOINC becoming idle. I would like to keep focus on the original problem, the computer dont werk rite when BOINC is werkin.

..

Gundolf Jahn,

You question is not understood. If the BOINCMgr application is launched, the system becomes slow. If the tray icon is closed, the BOINC and BOINC manager executables are removed from memory. That is as clear as can be explained.

..

Is there something the programmers have not corrected in regard to 'Snooze when user tells BOINC to snooze' or don't drain the system when BOINC has been configured to idle?

It has been a few years of exit BOINC or dont expect full performance.

I will note CUDA support sounds lackluster and unfortunately I may attempt to disable it completely. Does anyone recommend troubleshooting graphics core processing?

Sometimes the best cure is to stop trying to make BOINC do all things for all people.

If the current version(s) don't do want you want, then stop running BOINC on that computer.

Gundolf Jahn,

You question is not understood. If the BOINCMgr application is launched, the system becomes slow. If the tray icon is closed, the BOINC and BOINC manager executables are removed from memory. That is as clear as can be explained.

No.

The BOINC client exists of three parts

• The project applications do the real work, which is normally executed at low system priority and should therefore not interfere with your other work.
  
• boinc.exe starts and stops the project applications and does up- and downloading and other housekeeping tasks. Without boinc.exe running, BOINC does no work.
  
• The manager (boincmgr.exe) is only the Graphical User Interface, which helps you to control and configure the BOINC client. It also can start and stop boinc.exe.
  

If you install BOINC as a service (Protected Application Execution mode), boinc.exe runs even if nobody is logged on.

In normal mode, the manager launches boinc.exe at startup and stops it when finished. However, via the BOINC manager exit dialog, you can tell the manager not to stop the client when exited.

Usually, the manager takes only very few system resources, but (as I mentioned in my previous post) under certain conditions that can change. So, to determine what is slowing your computer down, you have to check with windows task manager which processes use your CPU when you snooze BOINC. If it's the project applications, the suspend command doesn't work for you. If it's boinc.exe or boincmgr.exe, perhaps something with your configuration is amiss.

And it's obviously not a BOINC problem per se, because the suspend (snooze) function does work for most of the other BOINC users.

Gruß,
Gundolf

Sekerob,

I am using the win32 and win64 installs of the latest release in the default installation (non-service, for the screen saver). I re-enabled the exit dialog and now see the new option of which you made a note. I will experiment with it.

..

Gundolf Jahn,

Please read the above statements.

The problem is definitely a BOINC issue, because the systems work after exiting the manager (and BOINC executable). When you make a statement about the snooze function working, what are you basing it on?

If the projects

do the real work, which is normally executed at low system priority and should therefore not interfere with your other work.

are you explaining that they have separate executables, and would you recommend removing one of the projects?

..

Lastly...

Les,

If the current version(s) don't do want you want, then stop running BOINC on that computer.

If it's broken, don't ask for help, get rid of it. How you made it to 600+ posts would probably amaze me.

are you explaining that they have separate executables

Yes.

It's, vaguely, like Windows.
Windows just controls the computer, and allows people to run their choice of programs, which can be anything.

BOINC, both the "client" (the 'worker', or 'daemon'), and the manager (the 'gui'), just provide an environment for people to run whatever files each project needs to do the work of that project. i.e. Download the programs, download the data, remember what stage of processing each work unit is up to, upload the data, decide which project to ask next for work, etc.

And snooze has always worked for me.

Gundolf Jahn,

Please read the above statements.

I did, but obviously you didn't read (or understand) mine. [edit]And if you didn't understand something, please ask.[/edit]

Did you even try to find out which of the three possible culprits is the CPU hog?

The problem is definitely a BOINC issue, because the systems work after exiting the manager (and BOINC executable).

The problem is not definitely a BOINC issue. It's possibly a BOINC issue, but you not willing to find out what's really happening.

When you make a statement about the snooze function working, what are you basing it on?

On my experience (it works for me) and on my reading the different fora (nobody else complains).

Gruß,
Gundolf

Gundolf Jahn,

When reading your post the assumption was that the applications were run as part of BOINC's executable.

It is now understandable a project is the cause.

Thank you for taking the time from your busy days. The makers of this application will now bear the burden of my unhappiness and lack of understanding (ha).

Ryan Lewis

P.S. Snooze duration would yet be advantageous. If this is an alarm clock, can't we have a nice one?