STEVE,

I prefer this line of thinking, general business users usually run Windows, graphics artist and publishers usually run Macs, and scientists usually run Linux. Almost all of the top 500 super-computers in the world run on Linux. I'm guessing that most of the scientific research applications natively run on Linux. It was easier for the GPUGRID scientist to get the QC CPU app running on Linux PC's so that was the initial release.

They tried to get the QC CPU to run on Windows a few months ago using the Windows Subsystem for Linux (WSL) but ran into problems with inconsistency between Windows releases. This is their next attempt to get the QC app to run on Windows. Looks like this one might work when they get the parameters set up for the size of tasks involved.

Well I tried to install a <project_max_concurrent> into the app_config but the beta work units just ignore that restriction. They were utilizing all 20 threads on the computer and starving the GPUs for resources. So I've stopped the beta for now on the machines. I have to rebuild a computer anyway this week so I think I will strip out the GPUs and leave the 16 thread CPU and install a 4 TB HDD. That should be enough I think for the beta work units and I will leave that machine only for those work units.

---

Well I tried to install a <project_max_concurrent> into the app_config but the beta work units just ignore that restriction.

You could try:

<app_config>
<app>
  <name>QC_beta</name>
  <max_concurrent>4</max_concurrent>
</app>
</app_config>

That has worked for me in the past.

Jim1348 wrote:

That has worked for me in the past.

I tested yesterday Quantum Chemistry Beta for Windows and QC_beta app name works for limiting concurrent computing WUs.

Using <project_max_concurrent> is a problem since it counts all GG WUs. Also, they ran out of GPU WUs yesterday. The control of CPU & GPU projects should be completely separate.

<app_config>
<app>
    <name>acemdlong</name>
    <gpu_versions>
        <cpu_usage>1.0</cpu_usage>
        <gpu_usage>1.0</gpu_usage>
    </gpu_versions>
    <fraction_done_exact>1</fraction_done_exact>
</app>
<app>
    <name>acemdshort</name>
    <gpu_versions>
        <cpu_usage>1.0</cpu_usage>
        <gpu_usage>1.0</gpu_usage>
    </gpu_versions>
    <fraction_done_exact>1</fraction_done_exact>
</app>
<app>
    <name>QC</name>
    <max_concurrent>8</max_concurrent>
    <fraction_done_exact>1</fraction_done_exact>
</app>
<app_version>
    <app_name>QC</app_name>
    <plan_class>mt</plan_class>
    <avg_ncpus>4</avg_ncpus>
</app_version>
<app>
    <name>QC_beta</name>
    <max_concurrent>1</max_concurrent>
    <fraction_done_exact>1</fraction_done_exact>
</app>
<app_version>
    <app_name>QC_beta</app_name>
    <plan_class>mt</plan_class>
    <avg_ncpus>4</avg_ncpus>
</app_version>
</app_config>

Well I tried to install a <project_max_concurrent> into the app_config but the beta work units just ignore that restriction.

You could try:

<app_config>
<app>
  <name>QC_beta</name>
  <max_concurrent>4</max_concurrent>
</app>
</app_config>

That has worked for me in the past.

Thanks Jim, I'll give that a shot later this week when I get back to those computers. Since there doesn't appear to be any more beta at the moment. I"ll put that in the app_config for when and if those betas return.

---

Two tasks have been frozen at 1,098% despite they ahievied it very quickly. I dont't think the app is good, yet...

Two tasks have been frozen at 1,098% despite they ahievied it very quickly. I dont't think the app is good, yet...

None of the BETA Wu's freeze up on my Box but it's 50/50 whether they get a computation error or not, They all seem to run 30 Min's even if they get the computation error, some finish okay but show up as Invalid here at the site ...

---

STE\/E

Two tasks have been frozen at 1,098% despite they ahievied it very quickly. I dont't think the app is good, yet...

My "_TONI_" wus for linux stuck at 10% and time remaining continue to grow up

Off to a rough start but think I got the kinks worked out. Got my 16 thread i7 on an Alphacool 360mm Radiator. 3 work units at a time with 4 threads, holding around 61-62C. Will see how it runs over the next 24 hours.

---

So this is the biggest one that I've crunched so far.

---

Starting to see lot of big ones lately but still none of those Giant one that we had a few months ago.

20239542 15931887 13 Feb 2019 | 4:52:27 UTC 13 Feb 2019 | 10:28:09 UTC

Completed and validated 5,123.56 19,627.41 1,235.32 Quantum Chemistry v3.31 (mt)

---

Starting to see lot of big ones lately but still none of those Giant one that we had a few months ago.

It is not as much fun working on the small ones. Maybe when they get the Windows app developed, they will have enough users that they can offer "small" and "large" work units, as defined by disk requirements (or even main memory).

Starting to see lot of big ones lately but still none of those Giant one that we had a few months ago.

It is not as much fun working on the small ones. Maybe when they get the Windows app developed, they will have enough users that they can offer "small" and "large" work units, as defined by disk requirements (or even main memory).

Are they working on a Windows app?

Thanks!

Are they working on a Windows app?

Very much so. I think they are making progress.
http://www.gpugrid.net/forum_thread.php?id=4790

Current test WUs are limited to 30GB, but many are failing because the limit is hit. I will need to raise the limit (the production QC app is 60 GB).

Wow, these things are going to be rough on SSD drive life. How large are the uploads and downloads?

Wow, these things are going to be rough on SSD drive life. How large are the uploads and downloads?

They have gone back to small ones. Running 11 of them on my i7-8770 (single core), my project folder is only 2.1 GB. It is no fun at all.

Current test WUs are limited to 30GB, but many are failing because the limit is hit. I will need to raise the limit (the production QC app is 60 GB).

Wow, these things are going to be rough on SSD drive life. How large are the uploads and downloads?

You could do like I did and install HDD. Those are fairly reasonable in price.Still have OS on the SSD but have BOINC installed on the HDD. Or if it's a new system, just install a HDD. I think I got 4 TB HDD for like $110 USD

---

I've had a few "error while computing" for QC tasks on linux recently. I had 4 on Feb 14th and 3 on Feb 13th but none today yet.

<core_client_version>7.9.3</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
17:04:03 (7591): wrapper (7.7.26016): starting
17:04:03 (7591): wrapper (7.7.26016): starting
17:04:03 (7591): wrapper: running /usr/bin/flock (/var/lib/boinc-client/projects/www.gpugrid.net/miniconda.lock -c "/bin/bash ./miniconda-installer.sh -b -u -p /var/lib/boinc-client/projects/www.gpugrid.net/miniconda &&
                      /var/lib/boinc-client/projects/www.gpugrid.net/miniconda/bin/conda install -m -y -p qmml3 --override-channels -c defaults  -c gpugrid  --file requirements.txt ")
Python 3.6.5 :: Anaconda, Inc.

# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<

`$ /var/lib/boinc-client/projects/www.gpugrid.net/miniconda/bin/conda install -m -y -p qmml3 --override-channels -c defaults -c gpugrid --file requirements.txt`

  environment variables:
                 CIO_TEST=<not set>
               CONDA_ROOT=/var/lib/boinc-client/projects/www.gpugrid.net/miniconda
                     PATH=/usr/bin:/bin
       REQUESTS_CA_BUNDLE=<not set>
            SSL_CERT_FILE=<not set>

     active environment : None
       user config file : /var/lib/boinc-client/.condarc
 populated config files : 
          conda version : 4.5.4
    conda-build version : not installed
         python version : 3.6.5.final.0
       base environment : /var/lib/boinc-client/projects/www.gpugrid.net/miniconda  (writable)
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/linux-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/pro/linux-64
                          https://repo.anaconda.com/pkgs/pro/noarch
                          https://conda.anaconda.org/gpugrid/linux-64
                          https://conda.anaconda.org/gpugrid/noarch
          package cache : /var/lib/boinc-client/projects/www.gpugrid.net/miniconda/pkgs
                          /var/lib/boinc-client/.conda/pkgs
       envs directories : /var/lib/boinc-client/projects/www.gpugrid.net/miniconda/envs
                          /var/lib/boinc-client/.conda/envs
               platform : linux-64
             user-agent : conda/4.5.4 requests/2.18.4 CPython/3.6.5 Linux/4.15.0-45-generic linuxmint/19.1 glibc/2.27
                UID:GID : 122:129
             netrc file : None
           offline mode : False


V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V

CondaHTTPError: HTTP 504 GATEWAY_TIMEOUT for url <https://conda.anaconda.org/gpugrid/linux-64/repodata.json>
Elapsed: 00:59.680897
CF-RAY: 4a92d5abb8af46f2-EWR

A remote server error occurred when trying to retrieve this URL.

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request.  The problem may be spurious, and will resolve itself if you
try your request again.  If the problem persists, consider notifying the maintainer
of the remote server.

A reportable application error has occurred. Conda has prepared the above report.
Upload successful.
17:06:11 (7591): /usr/bin/flock exited; CPU time 14.574405
17:06:11 (7591): app exit status: 0x1
17:06:11 (7591): called boinc_finish(195)

</stderr_txt>
]]>

Yeah I got a bunch of those as well. I think it's having an issue either downloading or connecting to get the required data. Doesn't happen often but when does, it usually results in numerous errors.

---