Forum > Windows

BOINC as library

<< < (9/9)

Raistmer:
Yes.... but if it would be multicore there were multi seti/einstein processes to eat CPU too ;)
It seems my version still not appropriate for profiling, it better suits for debugging - checkpointing broken.

Jason G:

--- Quote from: Raistmer on 23 Nov 2007, 01:11:09 pm ---Yes.... but if it would be multicore there were multi seti/einstein processes to eat CPU too ;)
It seems my version still not appropriate for profiling, it better suits for debugging - checkpointing broken.

--- End quote ---

LOL, Good point, though you would tend to use the fully loaded cores profile data just for overall system performance analysis rather than program profile information.  You would stop boinc for deeper module profile to not obscure the run.

Checkpointing? sounds like boincapi problem maybe

Josef W. Segur:

--- Quote from: Raistmer on 23 Nov 2007, 01:11:09 pm ---...checkpointing broken.
--- End quote ---

The default checkpoint interval is 300 seconds. When running with BOINC, the "Write to disk" preference overrides that, when running standalone you need to use an init_data.xml file to supply that and maybe a useful memory size. The knabench package has a suitable one, but I often use this simpler one:
-----------------------------------------------------------------------------
<app_init_data>
<wu_cpu_time>0</wu_cpu_time>
<checkpoint_period>60.000000</checkpoint_period>
<host_info>
    <m_nbytes>134217728.000000</m_nbytes>
</host_info>
</app_init_data>
-----------------------------------------------------------------------------
                                                       Joe

Raistmer:
Thank you, but my app does write checkpoint (every 300 sec only maybe but it does). It cant restore computation state from saved data - that i meant when wrote "checkpointing broken".

Navigation

[0] Message Index

[*] Previous page