Shoot, they do have a lot of possible stumbling blocks there. Bummer.

Rodrigo

[QUOTE=TheMawn;368313]CPUID's HWMonitor is a good tool for monitoring certain things you may not have considered. In my case, it was the HDD temperature.

I do close my laptop monitor while crunching over a long period of time, BUT my graphics are integrated to the CPU and it has a 25W power limit. With a dedicated GPU and a stronger CPU, the overall power consumption is likely to be much higher. HWMonitor can help with that, too.

While I do close the lid, I make sure to at least leave the air intake hanging over the side of a table (or better yet, I prop the laptop on its side pointing the exhaust straight up) to improve things in that regard. HWMonitor logs the max temperature it sees so over the course of a few hours or so you can get a good idea of the range of temperatures your hardware goes through. The highest CPU temperature difference I see is 60C if it's on a flat service, 55C if it hangs over the edge and 50C if it's propped on its side. The average temperature seems to be about 5C less than the max.

Leaving my monitor flap open doesn't affect my CPU temperature but it does affect the hard drive in a small way. Flat, with the lid closed, the hard drive temperature HAS reached 58C once, but I think a windows update ran the hard drive during that time. Usually the hard drive never goes over 50C and the current temperature hovers around the upper-mid 40's.


Long story short, if you ARE committed to using your laptop for GIMPS, expect that you're going to be harming your laptop's life expectancy, though you may not do so in a noticeable way: my four-year-old laptop is a bit sluggish after intermittent Starcraft II, a few other easier games, and a year of P-1 with GIMPS, but it still functions very well otherwise.

Get something to log hardware temperature (and keep the max value) and slowly inhibit cooling to see what you can and can't get away with. Watch for CPU (if you're using it), GPU and HDD temps (and RAM if you happen to have such a thing). Start with an A-frame or propping the laptop on its side, open, and see what you get. Then close it. Then lay it flat on a surface with the vents nice and clear.

If at any point the temperature gets outside your comfortable range, you'll have to make sure you can avoid whatever that cooling configuration was. For me it was seeing my CPU hit 88C and HDD hit 58C when I decided that I needed to have the vents hanging over the side of the desk.[/QUOTE]
Thanks, you've given me a number of things to play with. I have GPU-Z on that laptop, but I'll get the HWMonitor.

Speaking of how to position the laptop, I have another laptop that does LL's which is set flat on a wicker chair over the bowl of the seat to help the airflow. :smile:

Rodrigo

Have you tried using the "blank screensaver"? Just might be the [STRIKE]solution[/STRIKE] workaround for all your problems.

That was a GREAT idea, axn! :tu: Setting the screensaver to "blank" may not cut the signal to the monitor, but it does keep all images off it. Slide a finger on the touchpad, screen comes back on, and the GHz-d/d is still humming at over 200.

Thanks a bunch.

Rodrigo

Is there a schedule on 0.14? 0.13 doesn't work with Windows 8 at the moment (requires newer drivers)

Also, mfakto with GCN passes -st2 on the latest commit build. :smile:

[QUOTE=kracker;369809]Is there a schedule on 0.14? 0.13 doesn't work with Windows 8 at the moment (requires newer drivers)

Also, mfakto with GCN passes -st2 on the latest commit build. :smile:[/QUOTE]
One tiny feature and I can send out a test version. As I can't improve performance a lot, I'm adding other fancy stuff ;-)

I just posted the win version of [URL="http://mersenneforum.org/mfakto/mfakto-0.14pre4/mfakto-0.14pre4-win.zip"]mfakto-0.14pre4[/URL]. It should be pretty much complete, except that I did not check my latest changes on Linux yet. I plan to do that next week. Sometimes valgrind finds some weird stuff that I better change for win too.

These are the changes:

[LIST][*]--perftest enhancements including GPU sieve evaluation (for optimizing GPUSievePrimes etc.)[*]successfully resync when the working directory was temporarily lost (ejected USB device or interrupted network drive)[*]save and reload compiled OpenCL kernels => reduce startup time (UseBinfile config variable)[*]MoreClasses config variable to allow for a "less classes" version for very short assignments (GPU sieve only)[*]BugFix: enforce GPUSieveSize being a multiple of GPUSieveProcessSize[*]FlushInterval config variable to fine tune the number of kernels in the GPU queue => address high CPU load issue of newer AMD drivers[*]MinGW build (thanks to kracker)[*]slight performance improvement for the montgomery kernels[*]improved English wording in program output, ini file etc. (thanks to kracker)[*]recognition of new GPUs (8xxx, R9, new APUs) (thanks to kracker)[*]added a warning when using VectorSize=1 (AMD driver issue (?), [URL]http://devgurus.amd.com/thread/167571[/URL])[*]fix for a small memory leak (~0.5kB per assignment)[*]and it should work on Win8.1[/LIST]I'm interested to hear
[LIST][*]is it really running on Win8.1?[*]when doing real tests with GPU sieving, what's the CPU load, is the performance slower or faster than before?[*]anything odd[/LIST]Observations so far:
[LIST][*] VectorSize=1 is not usable on AMD GPUs (see above). It works on Intel and AMD CPUs, and on NVIDIA GPUs (!)[*]When playing around with various ini-file-settings, it is sometimes necessary to manually delete the binary kernel cache file (see UseBinfile setting)[*]Yes, NVIDIA GPUs finally work, but only with these settings:[LIST][*]VectorSize=1[*]FlushInterval=6 (or lower, depending on the SieveSize)[*]SieveOnGPU=1[/LIST] [*]other settings crash the nvidia driver (out of resources), compiler (mfakto crash) or fail the selftest.[*]on a Quadro 2000M, mfakto runs at 57.7 GHz-days/day (mfaktc: 78.8 GHz-days/day), which is better than I expected.[*]As it runs on one non-AMD platform now, we should go for the HD4000 next.[/LIST]

Working on Win 8.1, HD 7770, Catalyst 14.1. :smile:

I have a crippled Acer Aspire MC605 desktop. Intel Pentium CPU G2030 at 3.0 GHZ ( x 2) and graphics "Intel IvyBridge Desktop". I installed Ubuntu 13.10 on this desktop.

Is thre a way to check if I can run mfakto on this PC? Where should I look?

EDIT: got lspci:

[code]
luigi@luigi-Aspire-MC605:~$ lspci | more
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0b)

[/code]

I'm afraid I can do nothing with this... :sad:

Luigi.

[QUOTE=ET_;369984]I have a crippled Acer Aspire MC605 desktop. Intel Pentium CPU G2030 at 3.0 GHZ ( x 2) and graphics "Intel IvyBridge Desktop". I installed Ubuntu 13.10 on this desktop.

Is thre a way to check if I can run mfakto on this PC? Where should I look?

EDIT: got lspci:

[code]
luigi@luigi-Aspire-MC605:~$ lspci | more

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)

[/code]I'm afraid I can do nothing with this... :sad:

Luigi.[/QUOTE]

Well, this is the same question as the HD4000 thing. You seem to have an OpenCL-enabled Intel-GPU, but as I don't have something like that, turnaround times for fixing/debugging things have been quite long.

Try to install the Intel GPU drivers (most likely some proprietary ones), maybe check the Intel forums for requirements to enable OpenCL. These drivers should also ship an "clinfo" binary that allows to see OpenCL details.

"cat /proc/cpuinfo" may also help to find details about which CPU type it is exactly.

And then I will provide the 0.14pre4 binary for Linux within the next few days (I still have a nasty SEGFAULT to iron out) ...

[QUOTE=Bdot;369988]Well, this is the same question as the HD4000 thing. You seem to have an OpenCL-enabled Intel-GPU, but as I don't have something like that, turnaround times for fixing/debugging things have been quite long.

Try to install the Intel GPU drivers (most likely some proprietary ones), maybe check the Intel forums for requirements to enable OpenCL. These drivers should also ship an "clinfo" binary that allows to see OpenCL details.

"cat /proc/cpuinfo" may also help to find details about which CPU type it is exactly.

And then I will provide the 0.14pre4 binary for Linux within the next few days (I still have a nasty SEGFAULT to iron out) ...[/QUOTE]

Here is my OpenCL system:

[code]
clDeviceQuery Starting...

1 OpenCL Platforms found

CL_PLATFORM_NAME: Intel(R) OpenCL
CL_PLATFORM_VERSION: OpenCL 1.2 LINUX
OpenCL Device Info:

1 devices found supporting OpenCL on: Intel(R) OpenCL

----------------------------------
Device Intel(R) Pentium(R) CPU G2030 @ 3.00GHz
---------------------------------
CL_DEVICE_NAME: Intel(R) Pentium(R) CPU G2030 @ 3.00GHz
CL_DEVICE_VENDOR: Intel(R) Corporation
CL_DRIVER_VERSION: 1.2.0.82248
CL_DEVICE_TYPE: CL_DEVICE_TYPE_CPU
CL_DEVICE_MAX_COMPUTE_UNITS: 2
CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3
CL_DEVICE_MAX_WORK_ITEM_SIZES: 8192 / 8192 / 8192
CL_DEVICE_MAX_WORK_GROUP_SIZE: 8192
CL_DEVICE_MAX_CLOCK_FREQUENCY: 3000 MHz
CL_DEVICE_ADDRESS_BITS: 64
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 958 MByte
CL_DEVICE_GLOBAL_MEM_SIZE: 3832 MByte
CL_DEVICE_ERROR_CORRECTION_SUPPORT: no
CL_DEVICE_LOCAL_MEM_TYPE: global
CL_DEVICE_LOCAL_MEM_SIZE: 32 KByte
CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 128 KByte
CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE
CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE
CL_DEVICE_IMAGE_SUPPORT: 1
CL_DEVICE_MAX_READ_IMAGE_ARGS: 480
CL_DEVICE_MAX_WRITE_IMAGE_ARGS: 480

CL_DEVICE_IMAGE <dim> 2D_MAX_WIDTH 16384
2D_MAX_HEIGHT 16384
3D_MAX_WIDTH 2048
3D_MAX_HEIGHT 2048
3D_MAX_DEPTH 2048
CL_DEVICE_PREFERRED_VECTOR_WIDTH_<t> CHAR 1, SHORT 1, INT 1, FLOAT 1, DOUBLE 1


clDeviceQuery, Platform Name = Intel(R) OpenCL, Platform Version = OpenCL 1.2 LINUX, NumDevs = 1, Device = Intel(R) Pentium(R) CPU G2030 @ 3.00GHz

System Info:

Local Time/Date = 18:48:04, 03/30/2014
CPU Name: Intel(R) Pentium(R) CPU G2030 @ 3.00GHz
# of CPU processors: 2
Linux version 3.11.0-15-generic (buildd@batsu) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) ) #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013


TEST PASSED

[/code]

Is it worth anything?

:smile:

Luigi