Posts by Link

1) Message boards : Number crunching : Some questions (Message 8129)
Posted 30 May 2019 by Link
Post:
I can only answer #2: with the anonymous platform mechanism. If you need help with that, you will need to post the entire <app> and <app_version> sections of the cuda application from your client_state.xml and also the corresponding <file_info>, because I don't have cuda devices. You can find that info also in the sched_reply_moowrap.net.xml.
2) Message boards : Wish list : Wish your next release would not look like it has a virus. (Message 8125)
Posted 24 May 2019 by Link
Post:
In general it's recommended to exclude BOINC data dir from scanning. This exe comes from distributed.net and not from Moo! project, so it's the wrong place to ask anyway.
3) Questions and Answers : Android : BOINC BETA version Android 7.14.1 (Message 8122)
Posted 8 May 2019 by Link
Post:
An other question: does this BOINC version supports remote login like the desktop versions, or do I still have to stay with NativeBOINC for that? Couldn't find anything about it in the release notes.
4) Questions and Answers : Windows : Runtime error: Microsoft Visual C++ Runtime Library (Message 8120)
Posted 27 Apr 2019 by Link
Post:
I have 2005 and 2015. Seems to be enough at least for the ati14 application.
5) Questions and Answers : Windows : Runtime error: Microsoft Visual C++ Runtime Library (Message 8118)
Posted 24 Apr 2019 by Link
Post:
I wouldn't worry much about one single error message, you don't have any error or invalid tasks in your list, so probably no real issue.
6) Message boards : Number crunching : CPU WU earn enough to bother??? (Message 8110)
Posted 9 Apr 2019 by Link
Post:
Well, CPUs get here the same 8 credits per block as GPUs, relative to other projects you will have to find out self, that might be different for each computer depending on CPU, RAM etc, but in general I'd say Moo! is paying quite good.

At the end it's your choise which projects you prefer to crunch, I for example try to use my CPUs for work that can't be done on GPUs.
7) Message boards : Number crunching : Is there anything wrong with the i686-apple-darwin (cuda31) app? (Message 8104)
Posted 10 Mar 2019 by Link
Post:
Or do these users have nothing better to do than abort WUs all day long instead of disabling them in the preferences if they don't want them?

Examples:
1
2
3
4
5
6

So far I have not seen any Windows or Linux users doing this.
8) Message boards : Number crunching : This is just weird, help needed! (Message 8103)
Posted 9 Mar 2019 by Link
Post:
Not too sure if I can go into this account, remove the letter I added and then correct the email address in order to transfer the credits over to my correct account?

No, this will not work, merging accounts is not supported by BOINC. Just remove Moo! Wrapper on that device and add it again using the right account.
9) Message boards : News : Releasing new version 1.5 apps (Message 8097)
Posted 20 Feb 2019 by Link
Post:
Is new version Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.05 (ati14) (beta test) running clean enough, as far as failure rates, to be moved from BETA to production and retire the older 1.04 (ati14) ?

Bill F

Running without any errors so far on my Radeon HD3850.
10) Message boards : Number crunching : AMD HD3850 not getting the CAL application on Windows 10 (Message 8095)
Posted 1 Feb 2019 by Link
Post:
OK, Problem solved, apparently we only get WUs for the beta application.
11) Message boards : Number crunching : AMD HD3850 not getting the CAL application on Windows 10 (Message 8094)
Posted 1 Feb 2019 by Link
Post:
I was rebuilding my desktop computer and it got a clean installation of Windows 10. Since then my GPU doesn't get new tasks (and the server won't tell me why):

31.01.2019 14:40:57 |  | Starting BOINC client version 7.12.1 for windows_x86_64
31.01.2019 14:40:57 |  | log flags: file_xfer, sched_ops, task
31.01.2019 14:40:57 |  | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
31.01.2019 14:40:57 |  | Data directory: C:\ProgramData\BOINC
31.01.2019 14:40:57 |  | Running under account Link
31.01.2019 14:40:58 |  | CAL: ATI GPU 0: ATI Radeon HD 3800 (RV670) (CAL version 1.4.1734, 512MB, 480MB available, 922 GFLOPS peak)
31.01.2019 14:40:58 | SETI@home | Found app_info.xml; using anonymous platform
31.01.2019 14:40:58 |  | Version change (6.10.18 -> 7.12.1)
31.01.2019 14:40:58 |  | Platform changed from windows_intelx86 to windows_x86_64
31.01.2019 14:40:58 |  | Host name: DESKTOP-4LQTQ5O
31.01.2019 14:40:58 |  | Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU E7300 @ 2.66GHz [Family 6 Model 23 Stepping 6]
31.01.2019 14:40:58 |  | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 syscall nx lm tm2 pbe
31.01.2019 14:40:58 |  | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.17763.00)
31.01.2019 14:40:58 |  | Memory: 6.00 GB physical, 7.62 GB virtual
31.01.2019 14:40:58 |  | Disk: 48.83 GB total, 34.29 GB free
31.01.2019 14:40:58 |  | Local time is UTC +1 hours
31.01.2019 14:40:58 |  | No WSL found.
31.01.2019 14:40:58 | rosetta@home | URL http://boinc.bakerlab.org/rosetta/; Computer ID 2402456; resource share 100
31.01.2019 14:40:58 | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 7792158; resource share 100
31.01.2019 14:40:58 | SETI@home | General prefs: from SETI@home (last modified 09-Oct-2015 10:23:09)
31.01.2019 14:40:58 | SETI@home | Host location: none
31.01.2019 14:40:58 | SETI@home | General prefs: using your defaults
31.01.2019 14:40:58 |  | Reading preferences override file
31.01.2019 14:40:58 |  | Preferences:
31.01.2019 14:40:58 |  | max memory usage when active: 3685.97 MB
31.01.2019 14:40:58 |  | max memory usage when idle: 3685.97 MB
31.01.2019 14:40:58 |  | max disk usage: 29.30 GB
31.01.2019 14:40:58 |  | (to change preferences, visit a project web site or select Preferences in the Manager)
31.01.2019 14:40:58 |  | Setting up project and slot directories
31.01.2019 14:40:58 |  | Checking active tasks
31.01.2019 14:40:58 |  | Setting up GUI RPC socket
31.01.2019 14:40:58 |  | Checking presence of 15 project files
31.01.2019 14:40:58 |  | Running CPU benchmarks
31.01.2019 14:40:58 |  | Suspending computation - CPU benchmarks in progress
31.01.2019 14:40:58 |  | Suspending network activity - user request
31.01.2019 14:41:29 |  | FP benchmark ran only 0.984375 sec; ignoring
31.01.2019 14:41:29 |  | FP benchmark ran only 1.234375 sec; ignoring
31.01.2019 14:42:47 |  | Fetching configuration file from http://moowrap.net/get_project_config.php
31.01.2019 14:44:28 | Moo! Wrapper | Master file download succeeded
31.01.2019 14:44:33 | Moo! Wrapper | Sending scheduler request: Project initialization.
31.01.2019 14:44:33 | Moo! Wrapper | Requesting new tasks for CPU and AMD/ATI GPU
31.01.2019 14:44:34 | Moo! Wrapper | Scheduler request completed: got 0 new tasks
31.01.2019 14:44:34 | Moo! Wrapper | No tasks sent
31.01.2019 14:44:34 | Moo! Wrapper | Tasks for CPU are available, but your preferences are set to not accept them
31.01.2019 14:44:34 | Moo! Wrapper | New computer location: home
31.01.2019 14:44:35 |  | Eine neue Version von BOINC ist verf├╝gbar (7.14.2). <a href=https://boinc.berkeley.edu/download.php>Herunterladen</a>
31.01.2019 14:45:09 | Moo! Wrapper | Sending scheduler request: To fetch work.
31.01.2019 14:45:09 | Moo! Wrapper | Requesting new tasks for AMD/ATI GPU
31.01.2019 14:45:10 | Moo! Wrapper | Scheduler request completed: got 0 new tasks
31.01.2019 14:47:05 |  | Resuming file transfers
31.01.2019 14:50:03 | Moo! Wrapper | update requested by user
31.01.2019 14:50:06 | Moo! Wrapper | Sending scheduler request: Requested by user.
31.01.2019 14:50:06 | Moo! Wrapper | Requesting new tasks for AMD/ATI GPU
31.01.2019 14:50:07 | Moo! Wrapper | Scheduler request completed: got 0 new tasks
31.01.2019 14:50:42 | Moo! Wrapper | Sending scheduler request: To fetch work.
31.01.2019 14:50:42 | Moo! Wrapper | Requesting new tasks for AMD/ATI GPU
31.01.2019 14:50:43 | Moo! Wrapper | Scheduler request completed: got 0 new tasks
31.01.2019 14:51:40 | Moo! Wrapper | work fetch suspended by user
31.01.2019 14:59:45 | Moo! Wrapper | work fetch resumed by user
31.01.2019 14:59:48 | Moo! Wrapper | Sending scheduler request: To fetch work.
31.01.2019 14:59:48 | Moo! Wrapper | Requesting new tasks for AMD/ATI GPU
31.01.2019 14:59:50 | Moo! Wrapper | Scheduler request completed: got 0 new tasks
31.01.2019 15:00:06 | Moo! Wrapper | work fetch suspended by user


This is this computer: 1179617.
The GPU was tested under Windows 10 in computer: 25042 and worked fine (yes, it's back to Windows 7, after the HDD failed I have finished the tasks on the old drive with Windows 7, but they were assigned to the GPU when it was under Windows 10).

As fas as I can tell BOINC recognizes the GPU as CAL device, CAL Version 1.4.1734 from Windows 10 1809, however I don't know if it has exactly the same driver version as on the old Windows 10 installation (I think it was 1509, not sure, I wasn't using that computer for a while).

Anyway, according to the sched_request_moowrap.net.xml the computer is asking for work for the GPU (I censored parts of it with #####):

<scheduler_request>
    <authenticator>#####</authenticator>
    <hostid>1179617</hostid>
    <rpc_seqno>8</rpc_seqno>
    <core_client_major_version>7</core_client_major_version>
    <core_client_minor_version>12</core_client_minor_version>
    <core_client_release>1</core_client_release>
    <resource_share_fraction>0.333333</resource_share_fraction>
    <rrs_fraction>1.000000</rrs_fraction>
    <prrs_fraction>1.000000</prrs_fraction>
    <duration_correction_factor>1.000000</duration_correction_factor>
    <allow_multiple_clients>0</allow_multiple_clients>
    <sandbox>0</sandbox>
    <dont_send_work>0</dont_send_work>
    <work_req_seconds>0.000000</work_req_seconds>
    <cpu_req_secs>0.000000</cpu_req_secs>
    <cpu_req_instances>0.000000</cpu_req_instances>
    <estimated_delay>0.000000</estimated_delay>
    <client_cap_plan_class>1</client_cap_plan_class>
    <platform_name>windows_x86_64</platform_name>
    <alt_platform>
        <name>windows_intelx86</name>
    </alt_platform>
    <code_sign_key>
#####
</code_sign_key>
<working_global_preferences>
<global_preferences>
   <source_project>http://setiathome.berkeley.edu/</source_project>
   <mod_time>1444378989.000000</mod_time>
   <battery_charge_min_pct>90.000000</battery_charge_min_pct>
   <battery_max_temperature>40.000000</battery_max_temperature>
   <run_on_batteries>0</run_on_batteries>
   <run_if_user_active>1</run_if_user_active>
   <run_gpu_if_user_active>1</run_gpu_if_user_active>
   <suspend_if_no_recent_input>0.000000</suspend_if_no_recent_input>
   <suspend_cpu_usage>0.000000</suspend_cpu_usage>
   <start_hour>0.000000</start_hour>
   <end_hour>0.000000</end_hour>
   <net_start_hour>0.000000</net_start_hour>
   <net_end_hour>0.000000</net_end_hour>
   <leave_apps_in_memory>1</leave_apps_in_memory>
   <confirm_before_connecting>0</confirm_before_connecting>
   <hangup_if_dialed>0</hangup_if_dialed>
   <dont_verify_images>0</dont_verify_images>
   <work_buf_min_days>0.250000</work_buf_min_days>
   <work_buf_additional_days>0.010000</work_buf_additional_days>
   <max_ncpus_pct>100.000000</max_ncpus_pct>
   <cpu_scheduling_period_minutes>1600.000000</cpu_scheduling_period_minutes>
   <disk_interval>60.000000</disk_interval>
   <disk_max_used_gb>100.000000</disk_max_used_gb>
   <disk_max_used_pct>60.000000</disk_max_used_pct>
   <disk_min_free_gb>0.000000</disk_min_free_gb>
   <vm_max_used_pct>75.000000</vm_max_used_pct>
   <ram_max_used_busy_pct>60.000000</ram_max_used_busy_pct>
   <ram_max_used_idle_pct>60.000000</ram_max_used_idle_pct>
   <idle_time_to_run>3.000000</idle_time_to_run>
   <max_bytes_sec_up>0.000000</max_bytes_sec_up>
   <max_bytes_sec_down>0.000000</max_bytes_sec_down>
   <cpu_usage_limit>100.000000</cpu_usage_limit>
   <daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb>
   <daily_xfer_period_days>0</daily_xfer_period_days>
   <override_file_present>1</override_file_present>
   <network_wifi_only>1</network_wifi_only>
</global_preferences>
</working_global_preferences>
<global_preferences>
    <source_project>http://setiathome.berkeley.edu/</source_project>
    <source_scheduler>http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi</source_scheduler>
<mod_time>1444378989</mod_time>
<max_ncpus_pct>100</max_ncpus_pct>
<cpu_usage_limit>100</cpu_usage_limit>
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<idle_time_to_run>3</idle_time_to_run>
<suspend_if_no_recent_input>0</suspend_if_no_recent_input>
<suspend_cpu_usage>0</suspend_cpu_usage>
<work_buf_min_days>0.25</work_buf_min_days>
<work_buf_additional_days>0.01</work_buf_additional_days>
<cpu_scheduling_period_minutes>1600</cpu_scheduling_period_minutes>
<disk_interval>60</disk_interval>
<disk_max_used_gb>100</disk_max_used_gb>
<disk_min_free_gb>0.001</disk_min_free_gb>
<disk_max_used_pct>60</disk_max_used_pct>
<ram_max_used_busy_pct>60</ram_max_used_busy_pct>
<ram_max_used_idle_pct>60</ram_max_used_idle_pct>
<leave_apps_in_memory>1</leave_apps_in_memory>
<vm_max_used_pct>75</vm_max_used_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<daily_xfer_limit_mb>0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
</global_preferences>
<global_prefs_source_email_hash>#####</global_prefs_source_email_hash>
<cross_project_id>#####</cross_project_id>
<time_stats>
    <on_frac>0.063340</on_frac>
    <connected_frac>0.922759</connected_frac>
    <cpu_and_network_available_frac>0.999503</cpu_and_network_available_frac>
    <active_frac>0.991596</active_frac>
    <gpu_active_frac>0.999965</gpu_active_frac>
    <client_start_time>1549015629.335522</client_start_time>
    <total_start_time>1548942058.157639</total_start_time>
    <total_duration>3424.747641</total_duration>
    <total_active_duration>3394.606829</total_active_duration>
    <total_gpu_active_duration>3394.606829</total_gpu_active_duration>
    <now>1549015639.243946</now>
    <previous_uptime>231.046707</previous_uptime>
    <session_active_duration>0.000000</session_active_duration>
    <session_gpu_active_duration>0.000000</session_gpu_active_duration>
</time_stats>
<net_stats>
    <bwup>22616.884402</bwup>
    <avg_up>6733.609931</avg_up>
    <avg_time_up>1549013512.196512</avg_time_up>
    <bwdown>175482.916001</bwdown>
    <avg_down>3701.437171</avg_down>
    <avg_time_down>1549013505.430737</avg_time_down>
</net_stats>
<host_info>
    <timezone>3600</timezone>
    <domain_name>DESKTOP-4LQTQ5O</domain_name>
    <ip_addr>192.168.1.30</ip_addr>
    <host_cpid>3b1f0ad753f9ea4ec1a2f8bd41872f80</host_cpid>
    <p_ncpus>2</p_ncpus>
    <p_vendor>GenuineIntel</p_vendor>
    <p_model>Intel(R) Core(TM)2 Duo CPU E7300 @ 2.66GHz [Family 6 Model 23 Stepping 6]</p_model>
    <p_features>fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 syscall nx lm tm2 pbe</p_features>
    <p_fpops>2785111110.511154</p_fpops>
    <p_iops>5580834840.000073</p_iops>
    <p_membw>500000000.000000</p_membw>
    <p_calculated>1548942089.298468</p_calculated>
    <p_vm_extensions_disabled>0</p_vm_extensions_disabled>
    <m_nbytes>6441693184.000000</m_nbytes>
    <m_cache>3145728.000000</m_cache>
    <m_swap>8186523648.000000</m_swap>
    <d_total>52427751424.000000</d_total>
    <d_free>34846277632.000000</d_free>
    <os_name>Microsoft Windows 10</os_name>
    <os_version>Professional x64 Edition, (10.00.17763.00)</os_version>
    <n_usable_coprocs>1</n_usable_coprocs>
    <wsl_available>0</wsl_available>
</host_info>
    <disk_usage>
        <d_boinc_used_total>357435250.000000</d_boinc_used_total>
        <d_boinc_used_project>0.000000</d_boinc_used_project>
        <d_project_share>11534105313.280001</d_project_share>
    </disk_usage>
    <coprocs>
<coproc_ati>
   <count>1</count>
   <name>ATI Radeon HD 3800 (RV670)</name>
   <available_ram>503316480.000000</available_ram>
   <have_cal>1</have_cal>
   <have_opencl>0</have_opencl>
   <req_secs>22464.000000</req_secs>
   <req_instances>1.000000</req_instances>
   <estimated_delay>0.000000</estimated_delay>
   <peak_flops>921600000000.000000</peak_flops>
   <CALVersion>1.4.1734</CALVersion>
   <target>3</target>
   <localRAM>512</localRAM>
   <uncachedRemoteRAM>2047</uncachedRemoteRAM>
   <cachedRemoteRAM>2047</cachedRemoteRAM>
   <engineClock>720</engineClock>
   <memoryClock>900</memoryClock>
   <wavefrontSize>64</wavefrontSize>
   <numberOfSIMD>4</numberOfSIMD>
   <doublePrecision>1</doublePrecision>
   <pitch_alignment>256</pitch_alignment>
   <surface_alignment>4096</surface_alignment>
   <maxResource1DWidth>8192</maxResource1DWidth>
   <maxResource2DWidth>8192</maxResource2DWidth>
   <maxResource2DHeight>8192</maxResource2DHeight>
    <atirt_detected/>
</coproc_ati>
    </coprocs>
<app_versions>
</app_versions>
<other_results>
</other_results>
<in_progress_results>
</in_progress_results>
</scheduler_request>


Note <req_secs>22464.000000</req_secs> in <coproc_ati> section. Not sure if <work_req_seconds>0.000000</work_req_seconds> is what it's supposed to be, but also according to work_fetch_debug the computer was asking for work for the GPU, so I guess it's OK like this.


And than the server sends back this:
<scheduler_reply>
<scheduler_version>713</scheduler_version>
<dont_use_dcf/>
<master_url>http://moowrap.net/</master_url>
<request_delay>31.000000</request_delay>
<project_name>Moo! Wrapper</project_name>
<send_full_workload/>
<userid>7335</userid>
<user_name>Link</user_name>
<user_total_credit>63648.000000</user_total_credit>
<user_expavg_credit>69.055939</user_expavg_credit>
<user_create_time>1392101735</user_create_time>
<email_hash>#####</email_hash>
<cross_project_id>#####</cross_project_id>
<external_cpid>#####</external_cpid>
<project_preferences>
<resource_share>0</resource_share>
<no_cpu>0</no_cpu>
<no_ati>0</no_ati>
<no_cuda>0</no_cuda>
<allow_beta_work>0</allow_beta_work>
<project_specific>
<dnet_id>#####</dnet_id>
<core_cpu>-1</core_cpu>
<core_ati>-1</core_ati>
<core_nv>-1</core_nv>
<core>-1</core>
</project_specific>
<venue name="home">
<resource_share>100</resource_share>
<no_cpu>1</no_cpu>
<no_ati>0</no_ati>
<no_cuda>0</no_cuda>
<allow_beta_work>0</allow_beta_work>
<project_specific>
<dnet_id>#####</dnet_id>
<core_cpu>-1</core_cpu>
<core_ati>-1</core_ati>
<core_nv>-1</core_nv>
<core>-1</core>
</project_specific>
</venue>
</project_preferences>
<host_total_credit>0.000000</host_total_credit>
<host_expavg_credit>0.000000</host_expavg_credit>
<host_venue>home</host_venue>
<host_create_time>1548942273</host_create_time>
<team_name></team_name>
<rss_feeds>
  <rss_feed>
    #####
  </rss_feed>
</rss_feeds>
<gui_urls>
  #####
</gui_urls>
</scheduler_reply>

No WUs, no reason why. The GPU crunched this WU just two days ago, so it *should* work.

Does anybody here have an idea, what's the issue? I was thinking about trying an older driver (for Windows 8), but I thought I ask before I start mess something up. Or do I need an older BOINC version for such an old GPU?


EDIT: I just disovered this: Message 8071. I'll try that later, maybe that's the problem.
12) Message boards : Number crunching : Why the Difference in Credit for ATI vs. Nvidia GPU (Message 5983)
Posted 19 Mar 2014 by Link
Post:
That's true if they were all the same then we wouldn't need too different manufacturers.

We need at least two different manufacturers for to keep the prices low and actually get every now and than something new and not same chip they sell since 20 years. But that's another story.
13) Message boards : Number crunching : Why the Difference in Credit for ATI vs. Nvidia GPU (Message 5980)
Posted 18 Mar 2014 by Link
Post:
Hi,

I am new in this project (crunch with Nvidia).
It seems that a great difference of credit for such a small difference in Gpu/Cpu time is "crazy".
Each GPU card work on the same project ! So same credit !

for example (0.2 cpu + 1 gpu)
run time 2072
cpu time 1050
credit : 256


No it's all got to do with how WELL it works, not THAT it works. If I put you and a 2 year old in the same room you both might be able to stack some blocks, but you of course would do it MUCH better and faster, therefore you would get many more cookies for it. When a project starts it chooses to either make itself work with Nvidia cards or AMD cards as the programming is MUCH different for each. It usually depends on the resources of the person or group running the project and who they know and what the programmer is most familiar with. Then when one kind is working they kind of 'port' the programming over to the other kind, meaning it will work but we are back to my example of you and the 2 year old. Some projects are lucky and big enough to have access to programmers who know both kinds of gpu's and then both kinds work very well. But that is FAR from the norm in my experience.

For instance at Einstein I can take my AMD 7970, a near state of the art gpu, and run a gpu unit but it is taking me over 6 hours to finish a single unit. My Nvidia 560Ti, a 5 or more year old gpu, can do the same unit in about 2.5 hours. The project favors Nvidia cards but does work with AMD cards.

That's one part of the story. The second is, that the chips are very different and the calculations one application does might not perform as well on one of them as on the other simply because the hardware design is not so good for that type of calculations.

Same aplies to CPUs btw., just an example: my Pentium M and my Athlon X2 are both crunching SETI, both the Multibeam and the Astropulse applications. The Pentium is ~20% faster on Astropulse than the Athlon, the Athlon is ~20% faster on Multibeam. Not because the devs don't know how to optimize the applications for each of the CPUs, but in this particular case probably mostly because the Astropulse app benefits more from the larger L2 cache of the Pentium CPU.





 
Copyright © 2011-2020 Moo! Wrapper Project