Thanks Daniel.
Would it be possible to backport this particular commit to 2.4.x branch? Can
you please point me to the commit where you made the change?
On 2018/02/24 03:02:28, Daniel Sun wrote:
> Hi Divij,
>
> `ConcurrentHashMap` does not provide atomic operation(e.g.
> check-and-put) u
lass, with a lot of functionality I do not need/want.
mg10c
Ursprüngliche Nachricht Von: Jochen Theodorou
Datum: 24.02.18 12:06 (GMT+01:00) An:
dev@groovy.apache.org Betreff: Re: Thread contention on GroovyClassLoader
sourceCache
On 24.02.2018 07:14, Daniel Sun wrote:
&
On 24.02.2018 07:14, Daniel Sun wrote:
Hi Jochen,
As a Groovy user, I prefer higher level API, e.g. `GroovyShell`,
`GroovyClassLoader` ;-)
This kind of functionality can be in a higher API of course, but I think
GCL needs to be split instead of having another "mode". I think
GroovyShel
Hi Jochen,
As a Groovy user, I prefer higher level API, e.g. `GroovyShell`,
`GroovyClassLoader` ;-)
Cheers,
Daniel.Sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
On 23.02.2018 23:24, Divij Vaidya wrote:
Hello,
My name is Divij and I am working on an application which requires
concurrent script compilation with a high throughput.
I am using version 2.4.12 and currently, I am not able to achieve high
throughput because the threads are waiting at the sy
Another thread for your reference:
http://groovy.329449.n5.nabble.com/Executing-Groovy-DSL-scripts-concurrently-tp5747234.html
Cheers,
Daniel.Sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
Hi Divij,
`ConcurrentHashMap` does not provide atomic operation(e.g.
check-and-put) util Java8. So I have achieved a fine-grained access control
to these caches[1], which is available in 2.5+. 2.5 beta-3[2] is out and RC
will be released soon, so please give it a try :)
Cheers,
Daniel.Sun
[
Hello,
My name is Divij and I am working on an application which requires
concurrent script compilation with a high throughput.
I am using version 2.4.12 and currently, I am not able to achieve high
throughput because the threads are waiting at the synchronized code block
at [1].
I propose remov
