PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise
1) Message boards : General discussion : I found my first prime! (Message 66418)
Posted 2493 days ago by Profile K LewisProject donor
Congratulations also.
2) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54895)
Posted 2873 days ago by Profile K LewisProject donor
One issue though...how do I set the device in the wwww.ini file? I have tried d=, device=, and gpuaffinity= in the file, but none will allow me to run on the secnd GPU.


Assuming platform 0 is the 9600GSO since that's working by default, then to get the 530 to work on the second instance of prpclient running, then the second wwww.ini file should probably contain these lines, the platform one being important:-
platform=1
device=1 (if device 0 isn't listed in the options)

Or to list them all type wwww -l from the cmd window.
3) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54768)
Posted 2875 days ago by Profile K LewisProject donor

But I still get the occasional "wwwwcl has stopped working" when the machine is using a lot of it's cores, do you need the prpclient_memleak.txt file?



I am getting this constantly, regardless of how many CPU cores are in use (even if only the wwwwcl active cores are in use). Basically, I complete one unit, begin another, and the stopped working thing happens. Based on the observed behavior, I wonder about other activity on the GPU more than CPU (e.g., when monitor sleeps, loading a web page, etc.)


Tweaking the t & b values for the windows build seems to help me to delay the occurrence, for WSS I use a low t whilst increasing my b value, for WFS a high t & b value, using the default values in the wwww.ini gave me the this error more frequently too, but these values will depend on your card.

The mac build seems to run smoothly all the time.
4) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54763)
Posted 2876 days ago by Profile K LewisProject donor
Debug builds on Windows will now list memory leaks. It was leaking some memory. That is now fixed. I also fixed the problem with reading the platform/device from the ini file. Windows users will need to wait for a build from rebirther.


The platform and device setting for the dual GPUs in the wwww.ini now seems to be working fine for me, although it might be nice to have it report in the console which device is in use.

But I still get the occasional "wwwwcl has stopped working" when the machine is using a lot of it's cores, do you need the prpclient_memleak.txt file?
5) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54759)
Posted 2876 days ago by Profile K LewisProject donor
Could not parse stats line in [wwww.log].


I had this error once after a not responding (memory leak error), deleting the wwww.log file resolved it.

For not being able to download WFS or WSS workunits, does renaming the latest app to wwww.exe work in reference to the prpclient.ini file, I think if the file is named something like wwwwclv215 or whatever, it won't work, wwwwcl.exe might've worked but I'm not at those computers at the moment so I can't say for sure.
6) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54736)
Posted 2877 days ago by Profile K LewisProject donor
I found the problem. I'll fix it tomorrow.


Brilliant :)
7) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54735)
Posted 2877 days ago by Profile K LewisProject donor
Thanks for the suggestion, but I had already tried setting those switches in the prpclient.ini too, it won't download if the switches are present, ( ERROR: the client must run wwww to use this server.), and if you try when you've a workunit present, prpclient then stops working immediately after finding a workunit is present.
8) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54733)
Posted 2877 days ago by Profile K LewisProject donor
If you only have one platform and device, then you are okay. If not, then I need to investigate.

I can build one for you or if you have Xcode (or can install Xcode), then you can do it yourself.


I figured out getting the mac prpclient 5.0.8 working from the source files, all's good for that part.

But, I have two windows machines that both have dual GPU's, it's those that I'd like to be able to utilise by setting the "device=" setting in the wwww.ini but whatever I set it to it just gets ignored. It might also be helpful to have it report what platform/device is being used when running it through the prpclient app.

The command line works with the manual settings, but they're just not being understood from the ini file.

9) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54726)
Posted 2877 days ago by Profile K LewisProject donor
I can't get it to read the platform and device settings from the wwww.ini file, it does read the last four lines for threads and blocks for WSS and WFS on both mac and windows, but not the other settings for me.

Is there a prpclient 5.0.8 build for the mac available?
10) Message boards : Project Staging Area : Call for wwwwcl beta testers (OpenCL) (Message 54540)
Posted 2880 days ago by Profile K LewisProject donor
With Rebirther's (64 bit) 2.1.3 program and the -l switch the output I get is:-

wwwwcl v2.1.3, a GPU program to search for Wieferich and WallSunSun primes
List of available platforms and devices
Platform 0 is a NVIDIA Corporation NVIDIA CUDA, version OpenCL 1.1 CUDA 4.1.1
Device 0 is a NVIDIA Corporation GeForce GTX 590
Device 1 is a NVIDIA Corporation GeForce GTX 590



Next 10 posts
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2020 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 1.74, 2.27, 2.33
Generated 5 Apr 2020 | 4:53:50 UTC