Odd results (meaning workunit runtime) under Linux with Hyperthreading

roadrunner_gs
roadrunner_gs
Joined: 7 Mar 06
Posts: 94
Credit: 3369656
RAC: 0
Topic 191726

At work I use two "server" (in fact Fujitsu-Siemens Esprimo with Intel Pentium 4 630 at 3000 MHz each) under SuSe Linux 10.1 two crunch for Einstein@home.
Because these clients do not have internet connectivity (in fact connectivity is not allowed) i use my own notebook (Intel Pentium M 1200) at my desktop to report the workunits under VMWarePlayer with a Fedora Core 6 Test 1.
I frankly copy the BOINC directories with a USB-stick from the clients onto my notebook and vice versa.
But the runtime on the clients is much to long for my flavor:

Intel Pentium 4 630 (3000 GHz)

WU: 13,50 C; ~ 17995 s
WU: 13,19 C; ~ 17119 s

first one
second one

Intel Pentium D 805 (2666 MHz) (comparison, runing Windows 2003 Server)

WU: 13,80 C; ~3440 s

next one

I do not think that Hyperthreading which is enabled on the Esprimos has that much influence on the workunit runtime.
Has anyone any ideas what is going on here?
(Mr. Machenschalk has been recomended to me ;) )

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4312
Credit: 250178064
RAC: 34733

Odd results (meaning workunit runtime) under Linux with Hyperthr

Have you the ability to compare the wall-clock running times of the tasks?

If I'd use the same client information (i.e. client_state.xml file) on two completely different machines (in this case even with different number of CPUs), I'll simply won't give anything about information such as benchmark or runtime. It may work to copy the whole BOINC directory to transfer tasks to other machines, but the Client isn't made for it and will most likely get confused.

BM

BM

roadrunner_gs
roadrunner_gs
Joined: 7 Mar 06
Posts: 94
Credit: 3369656
RAC: 0

Work is only allowed in the

Work is only allowed in the time between 06:00 pm and 06:00 am and the computers only get four and two half workunits in this time and this is consistent with the reported workunit time.

Annika
Annika
Joined: 8 Aug 06
Posts: 720
Credit: 494410
RAC: 0

I'm not quite sure if this is

I'm not quite sure if this is possible in your case, but afaik SuSe servers have a so-called "power savings" option in their kernel, so as long as the cpu supports it maybe the CPU is not running full speed at night? I think that option is mainly for laptops but you CAN use it on servers if the hardware supports it... I'm actually quite sure about that because one of our servers had problems with that because it was switched on by default and we didn't want it ;-) But, as I said, I have no idea if this is the case with the servers you are using for crunching. It was just an idea that came up in my mind because I'm a laptop user and have made similar experiences on my lappi when I couldn't let the CPU run full speed due to heat reasons in July.

Jim-R
Jim-R
Joined: 8 Feb 06
Posts: 12
Credit: 4352
RAC: 0

RE: I'm not quite sure if

Message 44647 in response to message 44646

Quote:
I'm not quite sure if this is possible in your case, but afaik SuSe servers have a so-called "power savings" option in their kernel, so as long as the cpu supports it maybe the CPU is not running full speed at night? I think that option is mainly for laptops but you CAN use it on servers if the hardware supports it... I'm actually quite sure about that because one of our servers had problems with that because it was switched on by default and we didn't want it ;-) But, as I said, I have no idea if this is the case with the servers you are using for crunching. It was just an idea that came up in my mind because I'm a laptop user and have made similar experiences on my lappi when I couldn't let the CPU run full speed due to heat reasons in July.


FYI, it's not just SuSe and it's not just on servers. I run Slackware 10.1 on one compter and Slackware 10.2 on another and both of them have this feature. It's a part of any late model Linux kernel. If it's built into the kernel there's nothing much you can do (afaik) except possibly with config files, but if it's built as a module you can disable loading the apm modules and it won't power down or throttle back. I run BOINC on both computers so I simply don't load the modules so both machines are "alive and kicking" at all times.

When asked a question and you are not sure of the right answer, I've found that the best answer is always "I don't know for sure, but I'll find out!"

RenaudKener
RenaudKener
Joined: 11 Jun 06
Posts: 91
Credit: 5614714
RAC: 0

RE: RE: I'm not quite

Message 44648 in response to message 44647

Quote:
Quote:
I'm not quite sure if this is possible in your case, but afaik SuSe servers have a so-called "power savings" option in their kernel, so as long as the cpu supports it maybe the CPU is not running full speed at night? I think that option is mainly for laptops but you CAN use it on servers if the hardware supports it... I'm actually quite sure about that because one of our servers had problems with that because it was switched on by default and we didn't want it ;-) But, as I said, I have no idea if this is the case with the servers you are using for crunching. It was just an idea that came up in my mind because I'm a laptop user and have made similar experiences on my lappi when I couldn't let the CPU run full speed due to heat reasons in July.

FYI, it's not just SuSe and it's not just on servers. I run Slackware 10.1 on one compter and Slackware 10.2 on another and both of them have this feature. It's a part of any late model Linux kernel. If it's built into the kernel there's nothing much you can do (afaik) except possibly with config files, but if it's built as a module you can disable loading the apm modules and it won't power down or throttle back. I run BOINC on both computers so I simply don't load the modules so both machines are "alive and kicking" at all times.

Please forgive me if I say a supudity...
But, if you allow a higher priority at "einstein..." the kernel wouldn't slow the computer.
By default, boinc's priorities are very low and the kernel can slow the processor if only low priorities jobs are running. If 1 or more high priorities jobs are running, the kernel won't slow the machine.

Sorry if I seem to be stupid, but work week was a hell and I am "burn out" till monday.

"Entia non sunt multiplicandam praeter necessitatem"
(OKHAM)

Annika
Annika
Joined: 8 Aug 06
Posts: 720
Credit: 494410
RAC: 0

I think you actually can

I think you actually can deactivate this feature or alter the settings... but of course I'm not sure if that is a smart thing to do if it's not really your server ;-).
This is what my SuSe manual says about power saving:

Quote:
16.5.1 Configuring the powersave Package
Normally, the configuration of powersave is distributed to several files:
/etc/sysconfig/powersave/common
This file contains general settings for the powersave daemon. For example,
the amount of debug messages (in /var/log/messages) can be increased
by increasing the value of the variable POWERSAVE_DEBUG.
/etc/sysconfig/powersave/events
The powersave daemon needs this file for processing system events. An
event can be assigned external actions or actions performed by the daemon
itself. For external actions, the daemon tries to run an executable file in
/usr/lib/powersave/scripts/. Predefined internal actions:
ignore
throttle
dethrottle
suspend_to_disk
suspend_to_ram
standby
do_suspend_to_disk
do_suspend_to_ram
do_standby
throttle slows down the processor by the value defined in
POWERSAVE_MAX_THROTTLING. This value depends on the current
scheme. dethrottle sets the processor to full performance. suspend_-
to_disk, suspend_to_ram, and standby trigger the system event for
a sleep mode. These three actions are generally responsible for triggering
the sleep mode, but they should always be associated with specific system
events.
The directory /usr/lib/powersave/scripts contains scripts for processing
events:
notify Notification about an event by way of the console, X window, or
acoustic signal.
screen_saver Activates the screen saver.
SUSE LINUX 303
switch_vt Useful if the screen is displaced after a suspend or standby.
wm_logout Saves the settings and logs out from GNOME, KDE, or other
window managers.
wm_shutdown Saves the GNOME or KDE settings and shuts down the
system.
If, for example, the variable POWERSAVE_EVENT_GLOBAL_-
SUSPEND2DISK="prepare_suspend_to_disk do_suspend_to_-
disk" is set, the two scripts or actions are processed in the specified order
as soon as the user gives powersaved the command for the sleep mode
suspend to disk. The daemon runs the external script /usr/lib/
powersave/scripts/prepare_suspend_to_disk. After this script
has been processed successfully, the daemon runs the internal action do_-
suspend_to_disk and sets the computer to the sleep mode after the
script has unloaded critical modules and stopped services.
The actions for the event of a sleep button could be modified as in
POWERSAVE_EVENT_BUTTON_SLEEP="notify suspend_to_disk".
In this case, the user is informed about the suspend by the external
script notify. Subsequently, the event POWERSAVE_EVENT_GLOBAL_-
SUSPEND2DISK is generated, resulting in the execution of the abovementioned
actions and a secure system suspend mode. The script notify
can be customized using the variable POWERSAVE_NOTIFY_METHOD in
/etc/sysconfig/powersave/common.
/etc/sysconfig/powersave/cpufreq
Contains variables for optimizing the dynamic CPU frequency settings.
/etc/sysconfig/powersave/battery
Contains battery limits and other battery-specific settings.
/etc/sysconfig/powersave/sleep
In this file, activate the sleep modes and determine which critical modules
should be unloaded and which services should be stopped prior to a
suspend or standby event. When the system is resumed, these modules
are reloaded and the services are restarted. You can even delay a triggered
sleep mode (in order to be able to save files). The default settings mainly
concern USB and PCMCIA modules. A failure of suspend or standby is
usually caused by certain modules. See Section 16.5.4 on page 307 for more
information about identifying the error.
304 16.5. The powersave Package
16
Power Management
/etc/sysconfig/powersave/thermal
Activates cooling and thermal control. Details about this subject are available
in the file /usr/share/doc/packages/powersave/README.
thermal.
/etc/sysconfig/powersave/scheme_*
These are the various schemes that adapt the power consumption to certain
deployment scenarios. A number of schemes are preconfigured and can be
used as they are. Custom schemes can be saved here.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.