Fair enough, and I agree. Though the least we could do is rotate in a Windows env, where Java runs with -client, to our Jenkins.
But simple-to-follow rules like "Don't use Arrays.copyOf; use System.arraycopy instead" (if indeed System.arraycopy seems to generally not be slower) seem like a no-brainer. Why risk Arrays.copyOf, anytime? Shouldn't we never use it...? Mike McCandless http://blog.mikemccandless.com On Thu, Jun 30, 2011 at 3:09 PM, Dawid Weiss <dawid.we...@cs.put.poznan.pl> wrote: >> I think it's important Lucene keeps good performance on "ordinary" >> machines/envs. > > Not that this voice will help in anything, but I think the above is > virtually impossible to achieve unless you have a bunch of machines, > OSs and VMs to continually test on and a consistent set of benchmarks > plotted over time... and of course check every single commit for > regression over all these combinations. And even then you'd always > find a case of something being faster or slower on some combination of > hardware/ software; optimizing for these differences makes little > sense to me (people struggling with performance on some weird > software/hardware combination can always change the VM vendor or a VM > switch). > > Sorry for being so pessimistically unconstructive... :( > > Dawid > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
