-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When starting up, MartShell reads the local registry file and downloads all the dataset configs from the various marts described in the registry. It does this every time, whether or not the registry is the default one (which redirects to a full config on our servers), or a 'local' one which explicitly sets direct connections to marts.
MartView and the Perl API have a caching mechanism in place which speeds this up, but MartShell (and its other martj friends) do not. Yet. It's on the long-term plan. :) So unfortunately at present there's no way of speeding it up, short of creating a local registry which points only to the exact datasets you require (as I notice has just been described by Syed whilst I was writing this...). cheers, Richard PS. ensembl-staging is for our internal use only... not sure what it's doing in the release branches (did you check out from a release branch?). It shouldn't be there! :) Maximilian Haeussler wrote: > Hi, > > I'm often using martshell.sh and started to like it. However it takes > quite a while to start up. I assume that this is because it is > downloading the registry from the ensembl server. The documentation > mentions "local" registry files for the clients so I've taken the file > ensembl-staging.xml from biomart-perl and trying to feed that into > martshell by exchanging defaultMartRegistry.xml with it. But the hosts > and ports in this file are not correct (127.0.0.1). Is there a better > file registry file for ensembl42's marts to download somewhere or do > you think this won't help to reduce startup time anyways? > > Thanks again, > Max > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5F8s4C5LeMEKA/QRAoaFAJ0Tg3qS6ygfc2eCjcWTp8sPYRfWYQCbB0JH 5DnZ6iv3dCE64rrrKZKKRi4= =9uXO -----END PGP SIGNATURE-----
