http://ark.intel.com/it/products/80818/Intel-Core-i5-4460S-Processor-6M-Cache-up-to-3_40-GHz

http://ark.intel.com/it/products/78867/Intel-Celeron-Processor-J1900-2M-Cache-up-to-2_42-GHz

---

http://ark.intel.com/it/products/80818/Intel-Core-i5-4460S-Processor-6M-Cache-up-to-3_40-GHz

http://ark.intel.com/it/products/78867/Intel-Celeron-Processor-J1900-2M-Cache-up-to-2_42-GHz

Wow, did not expect Intel marketing department SO bad... They even can't compare 2 devices with common set of options... What instruction set J1900 supports for example?

What could be easier than just to take set of options, form table and fill that table, for both devices. And not to invent new table for each one?....

Is this normal or strange?

No, it's not normal. Maybe for Win8 though... Use other tools as recommended.

I don't know if the results and %blankeds are ~similar enough for to make the conclusion:

They similar enough to say that -use_sleep slowdowns GPU too much in your case. But they definitely not similar enough to make any conclusions on overall performance of loaded device.
Blanking should be exactly zero for that. Cause blanking % says nothing about how blanking distributed inside task and how many separate blanking replacements was made.

What means the CPU time usage (in OS/BOINC phrasing)?
Thanks.

CPU time means how much time single logical CPU of particular host spent inside process' code.
As already stated, if process consists of many threads it can exceed wall-clock time for process. In case of AstroPulse that could happen only on NV hardware w/o -use_sleep and with heavely blanked task.

http://ark.intel.com/it/products/80818/Intel-Core-i5-4460S-Processor-6M-Cache-up-to-3_40-GHz

http://ark.intel.com/it/products/78867/Intel-Celeron-Processor-J1900-2M-Cache-up-to-2_42-GHz

Wow, did not expect Intel marketing department SO bad... They even can't compare 2 devices with common set of options... What instruction set J1900 supports for example?

What could be easier than just to take set of options, form table and fill that table, for both devices. And not to invent new table for each one?....

There have always been lots of holes in the data on the Intel site. You can really tell when you do a compare: http://ark.intel.com/compare/75048,78867

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I saw something strange on my J1900 board.

Normally, AFAIK, in past with WinXP x86:
Intel Core2 Extreme QX6700 (Intel's 1st 4-Core-CPU, with 2x 2-Core-chips inside):
I suspend all tasks in BOINC, just let run one task.
Task-Manager say 25% CPU usage - OK.

Intel Core2 Duo E7600 (2-Core-CPU):
I suspend all tasks in BOINC, just let run one task.
Task-Manager say 50% CPU usage - OK.

Now the strange ... with Intel Celeron J1900 (4-Core-CPU (2x L2-Cache, so maybe 'like' QX6700?)) and Win8.1 x64:
I suspend all tasks in BOINC, just let run one task.
Task-Manager say ~30% CPU usage (30% of the CPU) - strange.
Let run 2 tasks, 2x ~30% usage (60% of the CPU) - strange?
Let run 3 tasks, 3x ~30% usage (90% of the CPU) - strange! ;-)

The stock AP 7.09 (r2742) iGPU app use 0-3% CPU (up & down).
So finally up to ~93% CPU usage if 3x CPU + 1x iGPU tasks (on a J1900 CPU).

Is this normal or strange?


I tested live -use_sleep and without this settings (r2742):
Both times with: -v 0 -unroll 5 -ffa_block 1472 -ffa_block_fetch 368 -hp -tune 1 64 2 1 -oclFFT_plan 32 8 256 -cpu_lock -instances_per_device 1
With 4x AP CPU tasks simultaneously both times.
Without -use_sleep:
Run time 16 hours 55 min 28 sec (60,928 sec)
CPU time 34 min 2 sec (2,042 sec)
single pulses: 4
repetitive pulses: 1
percent blanked: 18.39
With -use_sleep:
Run time 18 hours 15 min 34 sec (65,734 sec)
CPU time 26 min 8 sec (1,568 sec)
single pulses: 6
repetitive pulses: 0
percent blanked: 15.48

I don't know if the results and %blankeds are ~similar enough for to make the conclusion:
With -use_sleep (compared to without -use_sleep):
Calculation time: +4,806 sec (1 hour 26 min)
CPU time usage: -474 sec (7 min 54 sec)

Before we start to make a comparison what this means (longer iGPU calculation times and less CPU time usage - means 'faster' CPU tasks calculations then) ... best settings for max whole PC RAC.

What means the CPU time usage (in OS/BOINC phrasing)?
From the above mentioned example with -use_sleep:
1,568 sec of the whole CPU, or (x4) 6,272 sec on one CPU-Core?

OK, enough until now.

Thanks.

Your system CPU load in Windows 8.1 with < 4 tasks running seems high to me. For comparison this is my J1900. Running Windows 7 & I have most of the annoying unused background processes turned off.
http://www.hal6000.com/seti/images/j1900_1-task.png
http://www.hal6000.com/seti/images/j1900_2-task.png
http://www.hal6000.com/seti/images/j1900_3-task.png
http://www.hal6000.com/seti/images/j1900_3-task_processes.png
http://www.hal6000.com/seti/images/j1900_4-task_processes.png
In my case since I use vnc to connect to the machine it adds some CPU usage normally 1-2% but sometimes 4-5%. That is reflected in 1 CPU task graph.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Actually the Intel Celeron J1900 it's classified as SoC (by the way all the Core generations with integrated memory controller and gpu belong to this taxonomy).
http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/pentium-n3520-j2850-celeron-n2920-n2820-n2815-n2806-j1850-j1750-datasheet.pdf
Note the GPIO interface...
The processor do have support for SSE4.1 and SSE4.2 s.i.m.d instructions set.

---

Actually the Intel Celeron J1900 it's classified as SoC (by the way all the Core generations with integrated memory controller and gpu belong to this taxonomy).
http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/pentium-n3520-j2850-celeron-n2920-n2820-n2815-n2806-j1850-j1750-datasheet.pdf
Note the GPIO interface...
The processor do have support for SSE4.1 and SSE4.2 s.i.m.d instructions set.

I think Intel classifies it as SoC because it functions without an external south-bridge. So the whole "system" is on the chip. The only external IC needed is memory. Some of their mobile Bay Trail SoC also include memory.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

From AstroPulse v7 rev 2742 <stderr_txt>:

CPUID:       Intel(R) Celeron(R) CPU  J1900  @ 1.99GHz 

     Cache: L1=64K L2=1024K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 

- - - - - - - - - -
Just curious, HAL9000's J1900 show BOINC as:
Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
[Microsoft Windows 7]

My J1900:
Intel(R) Celeron(R) CPU J1900 @ 1.99GHz [Family 6 Model 55 Stepping 8]
[Microsoft Windows 8.1]

@ HAL9000, you made something 'specially' that the 'CPUs [ ] infos' aren't shown?
- - - - - - - - - -

Since January '15 the Intel driver do a good job, everything work fine.
Contrary to the wisdom 'don't change things on a well running machine' (the following) ... ;-)

I use still the v10.18.10.3408 Intel driver from the driver DVD which came with the MoBo.
Maybe a newer driver would effect a speed difference (I hope a speed up! ;-)?
Where I can download newer (for SETI/AP apps recommended) and how I uninstall correct the old driver first before upgrade (until now I have just experiences with NVidia GPUs in this case)?

Thanks.

---

From AstroPulse v7 rev 2742 <stderr_txt>:

CPUID:       Intel(R) Celeron(R) CPU  J1900  @ 1.99GHz 

     Cache: L1=64K L2=1024K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 SSE4.1 SSE4.2 

- - - - - - - - - -
Just curious, HAL9000's J1900 show BOINC as:
Intel(R) Celeron(R) CPU J1900 @ 1.99GHz
[Microsoft Windows 7]

My J1900:
Intel(R) Celeron(R) CPU J1900 @ 1.99GHz [Family 6 Model 55 Stepping 8]
[Microsoft Windows 8.1]

@ HAL9000, you made something 'specially' that the 'CPUs [ ] infos' aren't shown?
- - - - - - - - - -

Since January '15 the Intel driver do a good job, everything work fine.
Contrary to the wisdom 'don't change things on a well running machine' (the following) ... ;-)

I use still the v10.18.10.3408 Intel driver from the driver DVD which came with the MoBo.
Maybe a newer driver would effect a speed difference (I hope a speed up! ;-)?
Where I can download newer (for SETI/AP apps recommended) and how I uninstall correct the old driver first before upgrade (until now I have just experiences with NVidia GPUs in this case)?

Thanks.

I modify boinc.exe to not display [Family A Model B Stepping C] information. I don't like how it messes up my computers view. I also modify it to show the exact ATI model name instead of a generic series name.
This is also why I don't change versions often. As I have to modify boinc.exe each time.

On the drivers the saying here is "if it isn't broke, don't fix it". With Intel that has been shown to be good. As they sometimes break the drivers to cause garbage results. So far I have had no problems with release 4061. Display Driver Uninstaller supports Intel drivers too, but I have installed over the top of the old driver the past few times without any issues.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Given iGPU uses system memory. I imagine memory CL times may effect iGPU run times. This is the memory I happen to be using in my system.
http://www.hal6000.com/seti/images/j1900_mem-config.png
It was from a project at work where we were throwing away things. So I helped myself to the memory instead of it going in the trash.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I hope you don't get 100+ PMs/day of other members who want to know how you mod BOINC. ;-)
It's a big deal?
'Advanced' SETI users like me could do this also?
For to prevent your PM inbox overflows, maybe you could explain it how you mod BOINC?

(@ all: BTW, why the stock BOINC software don't show the correct ATI/AMD GPU card name (series) like NVidia? It's an impossible feature?)

It's a pity that it's not longer possible to do this over the registry. :-(
I had an automatically task which were executed at every boot up, so not needed to do it manually after every switch off.

Thanks.

- - - - - - - - - -

It looks like you use same MHz + CL like I do:

My ASRock Q1900DC-ITX board is running with:
8GB G.Skill DDR3L-1333 SO-DIMM CL9 Dual Kit (2x4GB) - Low Voltage 1.35V - 1333MHz @ CL9-9-9-24 - F3-1333C9D-8GSL

---

I hope you don't get 100+ PMs/day of other members who want to know how you mod BOINC. ;-)
It's a big deal?
'Advanced' SETI users like me could do this also?
For to prevent your PM inbox overflows, maybe you could explain it how you mod BOINC?

(@ all: BTW, why the stock BOINC software don't show the correct ATI/AMD GPU card name (series) like NVidia? It's an impossible feature?)

It's a pity that it's not longer possible to do this over the registry. :-(
I had an automatically task which were executed at every boot up, so not needed to do it manually after every switch off.

Thanks.

- - - - - - - - - -

It looks like you use same MHz + CL like I do:

My ASRock Q1900DC-ITX board is running with:
8GB G.Skill DDR3L-1333 SO-DIMM CL9 Dual Kit (2x4GB) - Low Voltage 1.35V - 1333MHz @ CL9-9-9-24 - F3-1333C9D-8GSL

I've been telling people for years that I mod BOINC to do my bidding. Normally after the "How do you do that" & I tell them "With a hex editor" that normally scares them away. If you don't know what you are doing in a hex editor you can screw things up very quickly.
To me it isn't a big deal. There are several text string that are available to change so it is just a simple matter of blanking out the things I don't want or replacing the text where I want to change it.

Now here comes the "Don't try this at home kids!" section.
-Exit BOINC so it isn't running.
-Make a backup of boinc.exe so you have the original to go back to when something bad happens.
-Open your preferred hex editor application.
-Load boinc.exe
-Locate the text string you wish to change
Here we will be removing the [Family A Model B Stepping C] string from being dispalyed.
http://www.hal6000.com/seti/images/boinc_mod_1.png
-Replace the hex vales with zeros. DO NOT ADD OR DELETE DATA. Replace.
http://www.hal6000.com/seti/images/boinc_mod_2.png
-Save the modifications.
-Place the modified boinc.exe in your BOINC program directory & run as normal.

This is the same process I use for my Pentium III 850MHz machine. As it doesn't have and CPUID name data.

The reason they can't get the exact ATI GPU model name has to do with how NV & ATI respond to an API call asking for the GPU model name. They had trouble early on getting the actual GPU name from ATI cards. So they hard code the displayed name into groups to save time as I recall.
It seems they do something similar with the Operating System string for Windows as well. Given this machine is running Windows 10 & not Windows 8.1 as it is displayed with BOINC 7.2.42. Where BOINC 7.4.42 will display "Windows 10".

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Thanks! :-)

Is there a way to edit the ATI/AMD GPU name also, for to show the really installed GPU card?

Until now I don't have, but soon I will.

I'll inform me about the 'hex editors' later ...
You could recommend an 'easy' tool for 'beginner'?

Thanks.

---

Thanks! :-)

Is there a way to edit the ATI/AMD GPU name also, for to show the really installed GPU card?

Until now I don't have, but soon I will.

I'll inform me about the 'hex editors' later ...
You could recommend an 'easy' tool for 'beginner'?

Thanks.

One of the hex editors I use often can be had here.
Modifying the GPU strings is just as easy as the other example.

Find what BOINC is displaying.
http://www.hal6000.com/seti/images/boinc_mod_3.png
Then make it say what you would like.
http://www.hal6000.com/seti/images/boinc_mod_4.png

If you have two machines with different GPUs in the same family. Such as the string "AMD Radeon HD 7870/7950/7970/R9 280X series (Tahiti)". You would have to save different versions of boinc.exe for a HD7950 in one machine & a R9 280X in the other.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Thanks! :-)

Now I have enough 'houseworks' (to learn how to use a 'hex editor') for the next days or weeks ... ;-)

---

OK, I did this:

Old string "ATI unknown":
http://asteroidsathome.net/boinc/show_host_detail.php?hostid=110
(at the moment of post I didn't still contacted the servers of Asteroids@home which is set to No New Tasks)

New string "ATI Radeon HD 6570 (NI TURKS) {ASUS EAH6570/DI/1GD3(LP)}"
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4832843

The new string is long - I needed to overwrite also the next 2 strings (which are about low HD5xxx models)
Of course the new string ends with 00 byte

I found that [ ] should not be used in those strings - in BOINC log info is OK but the web page started to act strange (weird things after the name)
At first the new string was "ATI Radeon HD 6570 (NI TURKS) [ASUS EAH6570/DI/1GD3(LP)] " so the problem may be also the ending space


I used HxD - Freeware Hex Editor
http://mh-nexus.de/en/hxd/

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I myself wrote:

If I would add a NV GPU card to the J1900 PC ...

I set -cpu_lock for the Intel iGPU AP app.
I set -cpu_lock also for the NV GPU AP app.

Does this mean both apps are fixed at CPU-Core #0?
Or each GPU app get his own CPU-Core, #0 & #1?

Thanks.

- - - - - - - - - -
BilBg wrote:

Code for -cpu_lock is probably the same in all Raistmer apps.
So any app will see (at start) which cores are already in use by other running apps (if they also use -cpu_lock) and choose the first unused core (if unused core exists).

- - - - - - - - - -
BilBg wrote:

Code for -cpu_lock is probably the same in all Raistmer apps.
So any app will see (at start) which cores are already in use by other running apps (if they also use -cpu_lock) and choose the first unused core (if unused core exists).

Raistmer wrote:

Yep, they should to do so.... but was never really checked with few different types of GPU installed. And it's quite easy to test.
Just open TaskManager when both app have running instances. Then look in affinity menu item what CPUs are checked for what process.

But even if both GPU apps happened to be pinned to the same core it can be still better than allow them to freely float between cores. Also, it's known that -cpu_lock has great impact on ATi app. Worth to directly check and show what its impact on iGPU's one.

-cpu_lock : Enables CPUlock feature. Results in CPUs number limitation for particular app instance. Also attempt to bind different instances to different CPU cores will be made.
Can be used to increase performance under some specific conditions. Can decrease performance in other cases though. Experimentation required.
Now this option allows GPU app to use only single logical CPU.
Different instances will use different CPUs as long as there is enough of CPU in the system.
To use CPUlock in round-robin mode GPUlock feature will be enabled. Use -instances_per_device N option if few instances per GPU device are needed.

So, maybe -instances_per_device 2 will be needed in this case too. Check that.

- - - - - - - - - -
Raistmer wrote:

So, maybe -instances_per_device 2 will be needed in this case too. Check that.

BilBg wrote:

@Dirk
To clarify: this doesn't mean you have to run 2 instances on one GPU

You may even use -instances_per_device 4 (just to 'reserve' counter for max 4 apps running)
- since BOINC starts the apps it will still start only 2 apps (one per GPU) unless you change this by app_info.xml / app_config.xml

- - - - - - - - - -

OK, in ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt: -cpu_lock -instances_per_device 1
in ap_cmdline_win_x86_SSE2_OpenCL_NV.txt: -cpu_lock -instances_per_device 2 (I let run 2 tasks simultaneously on GT730 (app_info.xml CUDA/0.5))

The result in Task-Manager:
1 Intel iGPU app at Core#0
1 NV GPU app at Core#0 and 1 NV GPU app at Core#1

What I need to change, that 1 NV GPU app (1st) use Core#1 and 1 NV GPU app (2nd) use Core#2?
(And Intel iGPU app use still Core#0)

Thanks.


BTW. With the above mentioned settings, the Intel iGPU app/task calculation increased from 17hrs to 18.5hrs (since I added the GT730 VGA card).

---

try -instances_per_device 3

In ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt: -cpu_lock -instances_per_device 1
in ap_cmdline_win_x86_SSE2_OpenCL_NV.txt: -cpu_lock -instances_per_device 3

The same result in Task-Manager:
1 Intel iGPU app at Core#0
1 NV GPU app at Core#0 and 1 NV GPU app at Core#1

---

In ap_cmdline_win_x86_SSE2_OpenCL_Intel.txt: -cpu_lock -instances_per_device 1
in ap_cmdline_win_x86_SSE2_OpenCL_NV.txt: -cpu_lock -instances_per_device 3

The same result in Task-Manager:
1 Intel iGPU app at Core#0
1 NV GPU app at Core#0 and 1 NV GPU app at Core#1

You could try -cpu_lock_fixed_cpu 3 (or 4) for the Intel iGPU. That should work for now.

I expect Raistmer may modify the mutex implementation to make some future versions cooperate between different brand GPUs, but no promises...

                                                                   Joe