You’re right, it could be better, but I don’t think referring to stuff directly out of the ivy cache is the way to do it - we started with that approach and it was problematic (I forget how actually).
When you have a local copy of the repo, it’s actually not as big an overhead as it looks - we did some timings and found it was only 10-20% of the launch time. What really kills you is not having a local repo. We need to add an ant task to build a local copy of the repo, but for now, you can copy the one that comes with the full-deps download package. I think you just need to drop the directory containing the repo copy into your OG-Platform directory and it just gets picked up, although there might be a config tweak you need.
The other way we don’t really hit this internally is we launch from Eclipse. If you’re looking at the examples, you can launch the ExampleComponentServerDev class with these VM arguments:
-Dlogback.configurationFile=com/opengamma/util/test/warn-logback.xml -Xms4096m -Xmx4096m -XX:MaxPermSize=512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+CMSIncrementalPacing -ea
Give those two things a try.