Prev: help: enum cause failure in multi thread run
Next: jsf large form question ?
From: markspace on 16 Jul 2010 02:06
Kevin McMurtrie wrote:
>
> Wow, so much analysis of me and not the code!


Er, no, just the code, which is a micro benchmark. I don't doubt that
it's really faster, I just think that in a much larger app, the overhead
of property lookup would be effectively reduced to noise, or less. File
IO, network IO or some much larger data structure would most likely be
the bottleneck in a large app.
From: Kevin McMurtrie on 17 Jul 2010 03:09
In article <i1ostp$9rs$1(a)news.eternal-september.org>,
markspace <nospam(a)nowhere.com> wrote:

> Kevin McMurtrie wrote:
> >
> > Wow, so much analysis of me and not the code!
>
>
> Er, no, just the code, which is a micro benchmark. I don't doubt that
> it's really faster, I just think that in a much larger app, the overhead
> of property lookup would be effectively reduced to noise, or less. File
> IO, network IO or some much larger data structure would most likely be
> the bottleneck in a large app.

Of course it depends on the app. If you have a lot of dynamic
configuration options (DAL properties, remote service addresses, feature
switches, algorithm switches, internationalization, etc.) in a Map then
those few lines of code are worth the coding effort. It's something
that would be more likely on an enterprise web server where shutting
down for adjustments isn't an option.
--
I won't see Google Groups replies because I must filter them as spam
First  |  Prev  | 
Pages: 1 2
Prev: help: enum cause failure in multi thread run
Next: jsf large form question ?