The Update Blog - Page 4

ltd · 2010-12-18, 22:41

Network is back. Server was up all the time.
For the memory problem it starts to look as if my combination of prpnet 4.0.3, iodbc, and myODBC has a big resource leak. I will try to get other versions to compile tomorrow and then see if there is a better combination.

ltd · 2010-12-19, 08:39

Managed to get the most recent drivers to compile on my system and now they are working with the prpserver.
I will now restart the prpnet 4.0.3 test server again and have a look at memory consumption.
Keep fingers crossed.

ltd · 2010-12-19, 09:28

Stopped the test as the combination of application and odbc drivers is far from memory stable. Each returned result increases the virtual memory consumption by serveral MB.

japelprime · 2010-12-19, 11:23

Are you mixing 64 bit odbc drivers and 32 bit server platform ? Dont know if this is possible to do. Install wrong drivers.

ltd · 2010-12-19, 13:16

No all 32Bit.

mdettweiler · 2010-12-19, 15:46

Quote:

Originally Posted by ltd

Stopped the test as the combination of application and odbc drivers is far from memory stable. Each returned result increases the virtual memory consumption by serveral MB.

That sounds a lot like a bug Mark and I are currently in the process of investigating. At first I thought your issue sounded to be of much greater magnitude than ours (MB per connection, which with our smaller candidates would have consistently overloaded NPLB's servers within hours after starting the server), but then I tried looking at virtual memory instead of active memory: one of our private ports had a 256GB pagefile!

(Surely not coincidentally, it also happened to be in the middle of a memory-leak-induced crash at the time. Given that 256 is exactly a power of 2, it looks like that's the tipping point.)

Given that, I don't think there's much you can do to fix this bug in the immediate meantime, since I'm also getting it with somewhat-new database drivers on 64-bit Linux (Ubuntu 9.04). Mark is looking for the exact source of the memory leaks right now, but still has not yet pinned it down for sure to a specific library.

However, I expect you will actually be OK to just run the server with the memory leaks intact. Some of our servers have run for months and never reached critical levels because they didn't have high enough load; with PSP's n=9M+ tests, load shouldn't be too much of a problem. (Just make sure you have a fair amount of space on your pagefile drive...

)

ltd · 2010-12-19, 16:03

Problem is that the machine is only a virtual server so I am somewhat stuck with what i get. And that is at least to small to run prpnet 4 for a longer time.
A real server is not in my budget at the moment.
But as I have a at least running version now I will also try to help finding the reason for the memory leak.
As I have developed a long time in C++ (before switching to C#) and also have experience in masive multi threaded environments
there is at least a chance that i find something. And if not i will at least have refreshed my linux knowledge.
So for me it is a win win situation to look into the code.

japelprime · 2010-12-22, 12:26

Lars
Will that help if we just stop using the old LLR server ? Is there some one else using that server ? I can spend some time to change over to other server if you prefer.

ltd · 2010-12-22, 13:47

The old llrnet server is not running at the moment due to the fact that it throws a lua error(scripting used for the MySQl handling).
I was not able to find the error so far.

As there is not much hope to repair this please send me residues of the outstanding tests and I will import them by hand.

Best way to help the project at the moment is to run an "old"(2.7.x) prpnet client and copy the latest llr.exe(3.8.4) into it.
Sorry but that is at the moment my best suggestion.
First priority is to fix the prpnet problem and then I will look into lua and find out if I understand enough of this language to fix the problem.

For the prpnet server 4.0.x we are still fighting with the memory issue.
Problem is that we see the memory increase but have no clue so far what causes this.
We (rogue,mdettweiler, and me) have already tried several things but still we have no clear picture. Leak analyse tools show small leaks ( a handful of bytes when the loss is really in MB) and tests to isolate the problem seem to show that our best candidates for causing the error are in fact not the reason.

runesk · 2010-12-23, 09:14

Quote:

Originally Posted by ltd

T
Best way to help the project at the moment is to run an "old"(2.7.x) prpnet client and copy the latest llr.exe(3.8.4) into it.
Sorry but that is at the moment my best suggestion.
First priority is to fix the prpnet problem and then I will look into lua and find out if I understand enough of this language to fix the problem.

opyrt hinted about this update blog, and I've updated the packages on http://tools.1up.no/psp/prpclient/

2.4.7 clients for Windows, Mac (Intel) and Linux having 3.8.4 llr available there.

.R

ltd · 2010-12-23, 15:35

Some promising news on the prpnet 4.x server front.
Made some significant improvements on the memory issues.
Now I will run these servers internally till after Christmas to make sure they are stable enough to go public.

Stay tuned.

2010-12-19, 08:39	#35
ltd Apr 2003 772₁₀ Posts	Managed to get the most recent drivers to compile on my system and now they are working with the prpserver. I will now restart the prpnet 4.0.3 test server again and have a look at memory consumption. Keep fingers crossed. Last fiddled with by ltd on 2010-12-19 at 08:40

2010-12-19, 16:03	#40
ltd Apr 2003 1100000100₂ Posts	Problem is that the machine is only a virtual server so I am somewhat stuck with what i get. And that is at least to small to run prpnet 4 for a longer time. A real server is not in my budget at the moment. But as I have a at least running version now I will also try to help finding the reason for the memory leak. As I have developed a long time in C++ (before switching to C#) and also have experience in masive multi threaded environments there is at least a chance that i find something. And if not i will at least have refreshed my linux knowledge. So for me it is a win win situation to look into the code. Last fiddled with by ltd on 2010-12-19 at 16:10

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Whatever Joey does blog	jvang	jvang	107	2019-04-05 08:21
My daily (srly?) work blog	MisterBitcoin	MisterBitcoin	10	2018-03-30 19:35
No update possible	Max	Information & Answers	5	2009-01-20 18:12
Puzzle Blog	grandpascorpion	Puzzles	0	2008-07-07 22:53
Project Tools & Blog	Xyzzy	Lounge	6	2007-09-05 16:27

2010-12-18, 22:41	#34
ltd Apr 2003 2²×193 Posts	Network is back. Server was up all the time. For the memory problem it starts to look as if my combination of prpnet 4.0.3, iodbc, and myODBC has a big resource leak. I will try to get other versions to compile tomorrow and then see if there is a better combination.

2010-12-19, 09:28	#36
ltd Apr 2003 2²×193 Posts	Stopped the test as the combination of application and odbc drivers is far from memory stable. Each returned result increases the virtual memory consumption by serveral MB.

2010-12-19, 11:23	#37
japelprime "Erling B." Dec 2005 88₁₀ Posts	Are you mixing 64 bit odbc drivers and 32 bit server platform ? Dont know if this is possible to do. Install wrong drivers.

2010-12-19, 13:16	#38
ltd Apr 2003 2²×193 Posts	No all 32Bit.

2010-12-22, 12:26	#41
japelprime "Erling B." Dec 2005 130₈ Posts	Lars Will that help if we just stop using the old LLR server ? Is there some one else using that server ? I can spend some time to change over to other server if you prefer.

2010-12-22, 13:47	#42
ltd Apr 2003 1404₈ Posts	The old llrnet server is not running at the moment due to the fact that it throws a lua error(scripting used for the MySQl handling). I was not able to find the error so far. As there is not much hope to repair this please send me residues of the outstanding tests and I will import them by hand. Best way to help the project at the moment is to run an "old"(2.7.x) prpnet client and copy the latest llr.exe(3.8.4) into it. Sorry but that is at the moment my best suggestion. First priority is to fix the prpnet problem and then I will look into lua and find out if I understand enough of this language to fix the problem. For the prpnet server 4.0.x we are still fighting with the memory issue. Problem is that we see the memory increase but have no clue so far what causes this. We (rogue,mdettweiler, and me) have already tried several things but still we have no clear picture. Leak analyse tools show small leaks ( a handful of bytes when the loss is really in MB) and tests to isolate the problem seem to show that our best candidates for causing the error are in fact not the reason.

2010-12-23, 15:35	#44
ltd Apr 2003 2²·193 Posts	Some promising news on the prpnet 4.x server front. Made some significant improvements on the memory issues. Now I will run these servers internally till after Christmas to make sure they are stable enough to go public. Stay tuned.