PRPNet 3.0.0 Released

[rogue]

Originally Posted by Xentar

Server version 3.2.6
Just found this in the log file:

and so on, a few hundred times.

Then I restarted the server. But I saw, that it used about 160MB RAM before restarting. Another memory leak?

It is interesting that the e-mail ID was blank. I wonder if that is related to the problem. What are the lines in the log prior to this message?

[Xentar]

Originally Posted by rogue

It is interesting that the e-mail ID was blank. I wonder if that is related to the problem. What are the lines in the log prior to this message?

Ahh, sorry.
No, I removed the mail address, because I didn't want to post it here

Prior to this messages, there is just the usual "Work unit sent to client" and "Result received from client".

[rogue]

Originally Posted by Xentar

Ahh, sorry.
No, I removed the mail address, because I didn't want to post it here

Prior to this messages, there is just the usual "Work unit sent to client" and "Result received from client".

It probably was a memory leak of some type, but it is nearly impossible to debug with logs and since logging wasn't turned on, I don't know what to do.

[Xentar]

I think, there is still a small memory leak, in the prpserver version 3.2.6 (Windows).
When I restarted the server on [2010-05-24 01:12:27 GMT], the memory usage was about 9MB. Now [2010-05-25 21:21:25 GMT] it is already up to 26 MB.

[rogue]

Originally Posted by Xentar

I think, there is still a small memory leak, in the prpserver version 3.2.6 (Windows).
When I restarted the server on [2010-05-24 01:12:27 GMT], the memory usage was about 9MB. Now [2010-05-25 21:21:25 GMT] it is already up to 26 MB.

Could you export your db and send it along with your prpserver.ini file to me via e-mail?

[Xentar]

Done.

[rogue]

I am in the process of testing PRPNet 3.3.0 and am looking for alpha testers. So far the testing is going smoothly. There are many changes, especially to the server stats webpage. If you are interested PM me your e-mail address.

[rogue]

3.3.0 has proven to be extremely stable (thanks Lennart and PrimeGrid). I have a couple of cosmetic changes and am now releasing 3.3.1. Here is a summary of the changes from 3.2.6 to 3.3.1:

All:

• Code infrastructure changes WRT sockets. The Socket class was cumbersome. I changed it so that Socket is an ancestor class and that specific server/client/mail functionality would be in descendent classes.
• Buffer no more than 4000 bytes at a time before sending data across the socket. This should improve performance on large data transfers.
• Use a static buffer for receiving data from a socket.
• Use a static buffer when logging messages.

Client only:

• Fixed an issue when testing for twin primes.
• When the startoption is to report and abort, shut down the client immediately after communicating with the server.

Server only:

• Added maxclients= to prpserver.ini to limit how many concurrent clients the server will handle.
• Removed -u option for upgrading from version 2.x.
• Removed behavior to insert into UserPrimes at startup since nobody (that I know of) is using a version of 3.x that is pre-3.2.
• Renamed ClientThread.cpp to HelperThread.cpp.
• Changed threading architecture to address memory allocation issue.
• Do not set LastUpdateTime when a test is sent to a client.
• When sorting by LastUpdateTime, include DecimalLength as an additional criteria in case multiple rows have the same LastUpdateTime.
• Moved logic from ClientHandler.cpp to HelperThread.cpp.
• Added CompletedThru to group stats.
• Added CountInProgress to group stats.
• Added summary line to group stats.
• Added a new index to Candidate to improve performance.
• Fixed an issue with BIGINT datatypes. With this change a number of columns have been changed from varchar(20) to bigint.

Run this code in the server to upgrade the database for 3.3.0.

alter table Candidate modify k bigint;
alter table Candidate modify LastUpdateTime bigint;
alter table CandidateTest modify TestID bigint;
alter table CandidateGroupStats modify k bigint default 0;
alter table CandidateGroupStats modify MinInGroup bigint default 0;
alter table CandidateGroupStats modify MaxInGroup bigint default 0;
alter table CandidateGroupStats modify LeadingEdge bigint default 0;
alter table CandidateGroupStats add CompletedThru bigint default 0;
alter table CandidateGroupStats add CountInProgress int default 0;
alter table UserPrimes modify DateReported bigint;
alter table Candidate add index ix_bnck (b, n, c, k);

I do not to putting out new releases (outside of bug fixes) for a while due to a busy summer schedule.

You can d/l it from here.

[Mini-Geek]

The new version looks great so far.
I like the added info to the group stats.

[mdettweiler]

Looks good at first glance, and I look forward to testing it in detail on my personal server shortly. Quick question, though: does this use the same communication protocol as 3.2.6? i.e., should I expect any problems running a 3.2.6 client on the 3.3.1 server?

[rogue]

Originally Posted by mdettweiler

Looks good at first glance, and I look forward to testing it in detail on my personal server shortly. Quick question, though: does this use the same communication protocol as 3.2.6? i.e., should I expect any problems running a 3.2.6 client on the 3.3.1 server?

No. If there were any compatibility issues, I would have stated them.