Re: Groovy 5 - Performance / @CompileStatic
MG <mgbiz-yvYIh6MZAuFWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.lang.groovy.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Jochen,
1. I read your post multiple times, and after overcoming the initial
"How complicated is this, I thought the indy mechanism was supposed
to take care of that... ?" reaction of my brain ( ;-) ), I think I
can approximately follow what you were suggesting in broad strokes.
2. However "We have to keep the cost of (indy) initialization much
lower than we do right now" definitely gets my prize for the
TLDR/executive version ;-)
3. I just saw Eric offered to help with a potential prototype, which
would be great - maybe Grooyv indy will one day be as fast as its
non-indy counterpart, even under heavy stress... G-)
Cheers,
mg
Am 13.08.2025 um 21:28 schrieb Jochen Theodorou:
> I think it is the cost of initialization. We have to keep that much
> lower than we do right now. Sadly you are the only reacting to that
> mail so far. I thought I kept it simple enough...