sagax has quit [Read error: Connection reset by peer]
sagax has joined #jruby
ur5us_ has quit [Ping timeout: 248 seconds]
lucasb has quit [Quit: Connection closed for inactivity]
_whitelogger has joined #jruby
_whitelogger has joined #jruby
nirvdrum has joined #jruby
ur5us_ has joined #jruby
ur5us_ has quit [Ping timeout: 245 seconds]
Gacha has joined #jruby
Gacha has quit [Read error: Connection reset by peer]
drbobbeaty has quit [Ping timeout: 248 seconds]
lucasb has joined #jruby
<enebo[m]> kares: rdubya I put out new point releases of arjdbc 50-60. These just end up dr-itz fixes. Someone asked for new 50.x about a week or so ago.
xardion has quit [Remote host closed the connection]
<headius[m]> enebo: just pushed a change to make evalType final and at least specs passed locally
<headius[m]> getting down there on a simple times benchmark now
xardion has joined #jruby
<headius[m]> about half as long to run 100_000_000.times {} on graalvm EE and 10x on CE (which ends up faster than EE somehow)
<headius[m]> compared to 9.2.9 with indy yields turned on (they were off by default)
<headius[m]> Java 8 comparison is better than 2x faster on my branch
<headius[m]> if I don't enable indy yields on 9.2.9 then it's more like 4.5x
<enebo[m]> headius: sounds really good
<enebo[m]> It is a start. Once I restart that work I will update those getting started bits.
<headius[m]> oh nice
rusk has quit [Read error: Connection reset by peer]
B_gahcdha has joined #jruby
<headius[m]> seems to have passed with final evalType
<headius[m]> so that eliminates a thread-local set on every block entry
<headius[m]> eliminates the thread-local and the set
unknown_guy[m] has joined #jruby
rusk has joined #jruby
<headius[m]> so this looks decent so far
<headius[m]> I'm looking at the ideap graph for this on graal CE and considering next steps
<headius[m]> ideal graph
<headius[m]> the null self seems like the next thing to deal with
<headius[m]> we pass a null self into most yield paths, basically to indicate "get self from binding"
<headius[m]> that also triggers it to set self onto the frame
<headius[m]> so next question is why binding has a self when it already has a frame with self
<enebo[m]> we talked about this a couple of weeks ago...i think one thought was instance_eval
<headius[m]> yeah I suppose there are cases where you want the frame to still be the same but update only self
<headius[m]> need to make those the rare case rather than doing this dance all the time
<enebo[m]> yeah agreed. and documented since the number of things which set frame self is basically only two cases
ang-st has quit [*.net *.split]
ang-st has joined #jruby
eregon has quit [*.net *.split]
eregon has joined #jruby
drbobbeaty has joined #jruby
ndbroadbent[m] has quit [*.net *.split]
MarcinMielyskiGi has quit [*.net *.split]
lopex[m] has quit [*.net *.split]
B_gahcdha has quit [Remote host closed the connection]
ur5us_ has joined #jruby
gisela[m] has joined #jruby
ur5us_ has quit [Remote host closed the connection]
ur5us_ has joined #jruby
nirvdrum has quit [Ping timeout: 268 seconds]
lucasb has quit [Quit: Connection closed for inactivity]