If you get a chance, try 1.1.0 Beta 6. It should do even better.
So over the weekend we had a large database upgrade going on a critical system here, hence not many users in.
I thought i’'d play a little game with openfire, so I set it up with 2GB of memory friday evening and restarted the server. When I checked it on Sunday morning it was at 480MB. Monday morning: 690MB…
I’‘m still running beta three, so i’'ll give beta six a try tonight…
Josh
I tested beta 6 today. The memory issues seem to have gone :). The gateway plugin even uses less memory than before. Good work
Excellent! Thanks you all for testing! There are two things left on my list:
-
Finish up IRC MUC support (there’‘s not much to go, it’'s a pretty quick process)
-
Find out why logging in from multiple resources is broken
After that I will be putting out 1.1.0 unless someone stumbles up something huge. (literally it would have to be something huge to prevent 1.1.0 from coming out … I’‘m going to try to minimize things holding it up. There’‘s soooo many updates in this version that it’'s a travesty to keep it in beta much longer. ;D
Our memory leaks went away with beta 6 as well. We now idle at ~35mb and load seems to be just under 100 MB.
Excellent work Daniel, thanks for your support.
Josh
Jury’‘s still out on memory issues, but it’‘s not a runaway train like it has been in the past. I’'ve added Yahoo! back into the mix given your recent promotion, too. Currently relatively stable at about 40 MB in use.
jadestorm wrote:
- Find out why logging in from multiple resources is broken
This is huge, for me. I typically have 2 or 3 clients all connected using the same JID (and occasionally as many as 4). I’'m happy to test and provide feedback if you have any specific things you need looked at.
scottr wrote:
Jury’‘s still out on memory issues, but it’‘s not a runaway train like it has been in the past. I’'ve added Yahoo! back into the mix given your recent promotion, too. Currently relatively stable at about 40 MB in use.
I’‘m confused, it sounded like you were saying that you are still having leaks but then you said it was stable. =) Is it just that you haven’'t tested it very long yet?
jadestorm wrote:
- Find out why logging in from multiple resources is broken
This is huge, for me. I typically have 2 or 3 clients all connected using the same JID (and occasionally as many as 4). I’'m happy to test and provide feedback if you have any specific things you need looked at.
Yeah, it’‘s mega broken and I don’‘t know why. I can see it trigger what it’‘s supposed to but… nothing is happening right. I’'ll put out another beta when I have it fixed.
jadestorm wrote:
I’‘m confused, it sounded like you were saying that you are still having leaks but then you said it was stable. =) Is it just that you haven’'t tested it very long yet?
A few days is usually not enough, but for the first time I’‘ve seen memory usage drop. It was slowly creeping up (was 43 MB at one point), but when I logged in this morning it was down to 24 MB. Woohoo! I’'m convinced that this is essentially resolved.
Yeah, it’‘s mega broken and I don’‘t know why. I can see it trigger what it’‘s supposed to but… nothing is happening right. I’'ll put out another beta when I have it fixed.
Well, some things do happen right. I noted with interest that even while contacts often don’'t show as online when I sign on with a second client, status changes often (always?) cause the person to appear. I can also get things mostly sane by disabling a gateway, then re-enabling it.
Weird thing that may or may not be related is that legacy server status is often not reflected properly to my Jabber client. But, my server’'s been up for more than 30 days and may be confused.