[Logo] Serotonin Software Community
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
out of memory error (windows)  XML
Forum Index » Mango installation
Author Message
kuau

Initiate

Joined: 02/11/2009 13:13:19
Messages: 2
Offline

I've got out of memory errors because I was using the default windows JVM settings.
Now I have set the initial JVM size to 128 MB and the maximum to 256.
tomcat now shows as using 217MB of memory instead of 128MB. I also increased the size of my page file from 700 MB to 1.5 GB.
The computer is a lowly 1.5 GHZ celeron with 512 MB RAM.

I've had this error two nights in a row, the data purge seems to trigger it.

mlohbihler

Master
[Avatar]

Joined: 01/03/2007 22:48:52
Messages: 1454
Offline

What version of Mango are you using?

Best regards,
Matthew Lohbihler
mlohbihler

Master
[Avatar]

Joined: 01/03/2007 22:48:52
Messages: 1454
Offline

Also, check the system settings page. If your database is pretty big you'll likely get better performance using MySQL rather than Derby.

Best regards,
Matthew Lohbihler
kuau

Initiate

Joined: 02/11/2009 13:13:19
Messages: 2
Offline

version 1.7. I'll consider switching to mysql.

I have one instance on a dual core machine (ubuntu 8.04) with 2gb ram and the database size is 2gb (derby). no trouble there.

As for the windows instance that is having trouble, I found a couple of points that change every 15s as they are used as a 'watchdog' which were not set to be purged. I have set them to purge now after 2 days. ~11k pointvalues per day. I ran the purges manually and didn't get an out of memory error so I think they might work tonight as well.

Is there a practical limit to how many pointvalues mango can deal with? I think I'll be generating ~525k pointvalues per year that I'd like to hold on to.

I did get some errors in the log while purging:
mlohbihler

Master
[Avatar]

Joined: 01/03/2007 22:48:52
Messages: 1454
Offline

I recommend switching to MySQL. The errors that you are seeing there have to do with long running delete operations. The delete will hold a lock on the table, meaning that async operations will sit and wait. If the wait is too long, the error occurs. In a system like Mango there's not much that can be done about this. (Believe me, i've looked into it.) MySQL provides better performance and the possibility of running on a separate host.

The bottom line is: if you see a lot of these errors, scale back your data collection, lower your data retention periods, or get a faster database server.

Best regards,
Matthew Lohbihler
 
Forum Index » Mango installation
Go to:   
Powered by JForum 2.1.9 © JForum Team