web stats
Mirth Database growing out of control - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 02-18-2011, 10:04 AM
jim jim is offline
OBX.1 Kenobi
 
Join Date: Sep 2009
Posts: 35
jim is on a distinguished road
Default Mirth Database growing out of control

My Mirth Database is growing out of control:
600MB every 12 hours.

I'm running:
Windows 2008 64 bit
Mirth Connect 2.0.1 64 bit
PostgreSQL 8.4 32 bit
Java 6.23 64 bit

And my PostgreSQL database for Mirth is growing out of control. I have following parms set in PostgreSQL
postgresql.conf
shared_buffers = 256MB
autovacuum = on
autovacuum_vacuum_threshold = 1000

I tried the same above with PostgreSQL 9.0 64 bit
and had the following settings postgresql.conf:
shared_buffers = 128MB
track_counts = on
autovacuum = on
autovacuum_vacuum_threshold = 1000

With Either PostgreSQL 9.0 or 8.4 the database grows out of control. I was running Mirth 1.8.2 and was pretty satisfied with it.

I don't know if its the database or if its Mirth but now I suspect its Mirth 2.0.1. It must not be removing rows like it should.

If anyone out there knows what the problem is and how to fix it I would be much obliged. Its really frustrating to have to delete the entire mirthdb every day and then recreate it with the initialize command and then restore all my channels. What a hassle. I just need to know:
a. Is it Mirth 2.0.1?
b. Is it PostgreSQL?
c. Is it Java 6.23?
d. Is it Windows 2008 OS?

Thank you for your help. I like Mirth, but hey if this dog won't hunt, I'll have to find another.

- Jim
Reply With Quote
  #2  
Old 02-18-2011, 11:20 AM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

You left out some key information like how many messages you are processing on your channels, how many of those channels are storing messages and for how long, and how often your Mirth Connect server is set to prune messages. It's possible that you are receiving that many messages and storing them all without ever pruning any. If that's not the case I'm not sure what the issue could be, but there weren't any changes in Mirth Connect that would cause that.
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #3  
Old 02-18-2011, 11:22 AM
dans dans is offline
Mirth Employee
 
Join Date: Apr 2007
Location: Irvine, CA
Posts: 590
dans is an unknown quantity at this point
Default

Are you receiving a lot of messages? Large messages? How many rows does the message table contain? Are you pruning messages?
__________________
Daniel Svanstedt
Software Engineer
Mirth Corporation

Want professional services, support, and enterprise or virtual appliances? It's all available from the Mirth Corporation:
Mirth Support | Mirth Training | Mirth Appliances | Online Training | Developer Q&A

Don't forget, Mirth Support gives you access to all of our online training videos, and silver support gives you access to developer Q&As!
Reply With Quote
  #4  
Old 02-18-2011, 11:25 AM
jacobb jacobb is offline
Mirth Employee
 
Join Date: Aug 2006
Location: Irvine, CA
Posts: 1,218
jacobb is an unknown quantity at this point
Default

From your other thread it sounds like its the postgres log that's growing because of errors?

http://www.mirthcorp.com/community/f...ead.php?t=5104

Please try to keep all of your information in a single thread.
__________________
Jacob Brauer
Director, Software Development
NextGen Healthcare

Reply With Quote
  #5  
Old 02-25-2011, 12:14 PM
jim jim is offline
OBX.1 Kenobi
 
Join Date: Sep 2009
Posts: 35
jim is on a distinguished road
Default Problem solved

Discovered that with all our channels, if you store messages and prune after 1 day, it still takes up quite a bit of space. 4.5 GB of space just for the message table in mirthdb after 7 days with PostgreSQL db. Evidently Mirth stores a copy of the same HL7 message after each transformation and for each destination, plus quite a bit of space is used up just to store one message. If that's the way it works, I'm ok with that.

Performance problems were solved by adding CPUS and RAM.
Increased from 2 CPUs to 4 CPUs
Increased from 2GB Ram to 6GB Ram

now we are running fine on a Win2008 64 bit, Mirth 2.01 64 bit, and Java 6.23 64bit, and PostgreSQL 8.4 32 bit.
Reply With Quote
  #6  
Old 03-07-2011, 03:31 PM
edvanbaak edvanbaak is offline
Mirth Newb
 
Join Date: Aug 2010
Posts: 23
edvanbaak is on a distinguished road
Default

It's helpful to get an idea of how large the db might get - I've been wondering the same on some test channels we have. I guess as long as it's pruning, it'll hit some sort of relative size threshold.

Thanks for posting back that it's working.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 12:38 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation