Moreover, I'll add that we created DSPM to counter a problem with the
SimpleDbPM and MySQL (the famous "broken pipe" problem ... look at the
archive of the mailing list) and now, it is working greatly with that DB
(MySQL) on both Linux and Windows.
Anthony
David Smith a écrit :
I've bootstrapped to a database a few times in tests and the response
has always been faster than that. On a very under-powered laptop w/
WinXP SP2, it took no more than 30 minutes to a mysql db on the same
system. On a decent linux server system it took less than a minute.
I expected the difference given the severe increase in OS overhead and
much smaller system memory. The system swap got involved and that
kill the performance.
Some thing in your system is taking waaaayyy longer than it should.
If I were you, I'd be looking at:
1. Network issues (DNS, firewalls, etc., ...) between tomcat and the
db server.
2. Db driver performance (I've heard the MS supplied MS SQL JDBC
driver is very slow and there are faster third party drivers).
3. System resources. Be sure there is sufficient resources to prevent
Windows from swapping during the bootstrap. You may need to tune down
your JVM memory allocation if it in addition to the memory
requirements of the rest of the system forces the system swap.
Windows performance monitor, SysInternal's TCPMon, and SysInternal's
Process Explorer are all excellent tools for analyzing system
performance issues. There are also excellent tomcat performance
monitoring tools if it looks like Tomcat or Magnolia are at fault.
--David
john.mcclain wrote:
Howdy - I have been diligently trying multiple ways to get a fast and
reliable repository going - yes I know fast is relative, so I'll give
some stats
I configured a DataSourcePersistenceManager/Jboss/SqlServer
environment. Bootstrap took around 1.5 hours each for author and
public = 3 hours! It finally did complete with no errors in the log
files
I configured a SimpleDbPersistenceManager/jboss/SqlServer envronment.
Bootstrap is running now and we have passed the 15 minute mark and we
are still in Author with a lot of processing to go.
I am running JBOSS locally and sqlserver remotely over the network.
How can I debug what the problem is? Has anyone ever gotten a
jboss/sqlserver/XpersistenceManager install to run?
We are doing this because we have had problems using the
filePersistenceManager, AND we wnated our content in a DB. What are
the alternatives for SQL Server that don't employ the Enterprise
Edition?
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
