using large databases
"Appelt, Uwe" <[email protected]>
| Newsgroups | gmane.comp.db.mysql.java |
|---|---|
| Message-ID | <8E1D49EDFDE9AC4293FC4CBF125AC6641A0CB1@CEX20.ads.krz.uni-heidelberg.de> |
Dear Developers, i'm currently working on a very database intensive project. In fact, we have a bunch of computers (50-60), that could be used as a db-cluster, but unfortunatly those computers are part of a public available pool, so that we cannot run mysql as a classicly-fashioned dbms-cluster. instead, we developed a java-rmi cluster, where each host eats 'database jobs', when it is not loaded by an locally logged on user. these jobs actually consist of massive selecting data from a several gigabytes database (genetic data as provided by ensembl.org). as i saw (or guess) you are deploying embedded databases from the ressource dir, that also contains the data-dir as a jar-archive. but in the above case, it would not make any sense at all, to decompress a several gb-jar everytime, the java-app is started (which is actually done, when the user loggs off) => question: is it possible, to use connector/MXJ with a fully preconfigured mysql-directory including 'bin/mysqld', 'data/myhugedb/*.*' and a 'my.ini', which is already lying on a local harddrive? if so, i would preconfigure the database to be used by clusterclients as an embedded ressource on a standalone system and patch later on each clusterhost with the whole mysql-dir prior to install the java-app. would that make sense to you? thanks in advance and kind regards Uwe Appelt (Dipl. Inform. Med.) Universitätsklinikum Heidelberg Institut für Transplantationsimmunologie Friedrich-Ebert-Anlage 17 69117 Heidelberg Tel.: 06221 1370-22 Fax.: 06221 1370-45 [email protected] -- MySQL Java Mailing List For list archives: http://lists.mysql.com/java To unsubscribe: http://lists.mysql.com/[email protected]