-
1. Re: jdbc2.PersistenceManager with Postgres very slow!
adrian.brock Oct 3, 2003 8:02 AM (in response to crichard)Which jboss version are you using?
If you don't want to use guaranteed delivery,
you can send the message as non-persistent.
It is an option on the send.
The MessageCache mbean
controls the memory usage and
messages written to the cache.
If your db is slow, try file persistence, there are instructions
in jbossmq-service.xml on swapping it.
Regards,
Adrian -
2. Re: jdbc2.PersistenceManager with Postgres very slow!
crichard Oct 6, 2003 12:15 AM (in response to crichard)I am using version 3.2.2RC3.
Are the Mem Marks set in the -service.xml related to the jvm memory set in the run.sh? I have set the MaxMemoryMark to 896 and the High to 768. Setting it that high didn't seem to make any difference???
With regards to file persistance. Would that be an option considering that there will be a large amount of messages parsing thorugh my system on a daily basis(500 000+).
I can't to drop any messages either so persistance must stay on. -
3. Re: jdbc2.PersistenceManager with Postgres very slow!
adrian.brock Oct 6, 2003 2:09 AM (in response to crichard)The message cache stop you running out of memory.
If you can't afford to lose a message, it must persist the messages
to the db/file system.
WRT file system, try it. There is also a rolling logged pm
that is supposed to be faster, but I've never tried it.
Regards,
Adrian -
4. Re: jdbc2.PersistenceManager with Postgres very slow!
adrian.brock Oct 6, 2003 4:21 AM (in response to crichard)One thought. Does postgres automatically create primary key
indexes?
Regards,
Adrian -
5. Re: jdbc2.PersistenceManager with Postgres very slow!
stephanenicoll Oct 6, 2003 6:46 AM (in response to crichard)Good point.
I don't know but we are facing the same issues. I know my colleagues tuned the createSQL statement for MySQL (and we are creating the two tables ourselfves before starting Jboss for the first time)
Maybe working on that solution could help. If you find an optimized sql query, let us know
Regards,
Stephane -
6. Re: jdbc2.PersistenceManager with Postgres very slow!
crichard Oct 6, 2003 7:38 AM (in response to crichard)Yeah, Postgres creates the primary key index on it's own!
-
7. Re: jdbc2.PersistenceManager with Postgres very slow!
crichard Oct 6, 2003 7:40 AM (in response to crichard)Postgres creates primary key indexs on its own!
-
8. Re: jdbc2.PersistenceManager with Postgres very slow!
pun Oct 6, 2003 9:30 PM (in response to crichard)If the table is updated frequently, we must vacuum frequently. Having Indexes don't mean the indexes must be in use for PostgreSQL db.
Consider to use "explain" to check. -
9. Re: jdbc2.PersistenceManager with Postgres very slow!
adrian.brock Oct 7, 2003 5:35 PM (in response to crichard)I'd forgotten about vacuum.
It's like an object database in that respect.
Regards,
Adrian