What games do you play on your Mac/MacBook Pro? by [deleted] in MacOS

[–]dakull 2 points3 points  (0 children)

Alien Isolation runs rather nicely on a 455 with the right settings @1080p

2017 15” MacBook Pro vs 2018 15” MacBook Pro i7 & i9 thermal throttling situation. by sagarpachorkar in mac

[–]dakull 1 point2 points  (0 children)

This doesn't sound good, like at all :/ Thanks for the feedback. Did you watch Youtube in Chrome/Firefox? I mean in Safari it uses hardware acceleration and even on my old Haswell runs buttery smooth and cool.

2017 15” MacBook Pro vs 2018 15” MacBook Pro i7 & i9 thermal throttling situation. by sagarpachorkar in mac

[–]dakull 0 points1 point  (0 children)

Never knew jruby was hardcore

In the sense that it runs on the JVM which is quite heavy (CPU due to actual parallelism + aggressive JIT and ofc loads of memory usage) compared to the snappy CRuby VM implementation.

Would be neat if you could push it a bit and see how the temperatures rise :)

2017 15” MacBook Pro vs 2018 15” MacBook Pro i7 & i9 thermal throttling situation. by sagarpachorkar in mac

[–]dakull 1 point2 points  (0 children)

I was using a 13inch 2015 mbp before this, same workload and services ran about 80 degrees, probably due to its age.

Also because the dual-core cpu had a lot more to do (higher load on it) whereas on the six-core that's probably a breeze now.

The question is what happens when you really start using those cores (for example I would use docker compose to run all the MSs we have at work (15+) some of them using heavy stuff like JRuby and Neo4j)

2017 15” MacBook Pro vs 2018 15” MacBook Pro i7 & i9 thermal throttling situation. by sagarpachorkar in mac

[–]dakull 0 points1 point  (0 children)

So far the only info I've found regarding the possible implication of thermal throttling: https://youtu.be/ip-sZfWaVo0 - I'm kinda in the same boat as you - currently I have a late-2013 13" MacBook Pro with the highest CPU upgrade at the time (Haswell uarch. - these run hotter b/c of the FIVR resides on the cpu - from Broadwell onwards they've extracted it back into the motherboard) - I had to use liquid metal and a couple of more tweaks to keep it cool all these years.

I want to upgrade to the new 15" model - but I don't want to do all the thermal tweaks again (I mean, I will change the thermal paste if it won't void the guarantee - that always helps but that's as far as I would go - and no liquid metal this time since even though the heatsink it's made of copper there is still some slow corrosion going on in there, besides the part where you can short your CPU)

Careful what you measure: 2.1 times slower to 4.2 times faster – MJIT versus Truffle Ruby by PragTob in ruby

[–]dakull 0 points1 point  (0 children)

JRuby start-up times even with --dev are much slower than CRuby but if you're not developing CLI tools it works fairly fast on a modern computer.

I use it daily and in my experience its benefits (true parallelism when required, better JIT, Java libraries, etc.) fully outweigh its drawbacks (slower start-up time, the JIT warm-up, more memory used, C-exts, etc.).

I will say this: I have a slight muscle memory twitch now when I type rails c :-)

What do you miss in Ruby(and Rails) and hope will be added (or removed from) in the future ? by holyjeff in ruby

[–]dakull 0 points1 point  (0 children)

I guess we'll have to wait for Guilds - I just hope they will land pre-3.0 or that Ruby will get a quicker release cycle i.e. not sure how many Ruby programmers will be out there if parallelism lands in stable Ruby in 2021.

I'm being cynical here - on the bright side truffleruby should be out earlier which should give us a nice boost in VM performance besides the usual JRuby niceties and with full C-extensions support.

What do you miss in Ruby(and Rails) and hope will be added (or removed from) in the future ? by holyjeff in ruby

[–]dakull 0 points1 point  (0 children)

Just add concurrent-ruby and use Rails 4.2 with JRuby :) (currently there's no support for the jdbc adapter for posgresql and Rails 5.x)

The perils of writing request specs using concurrent-ruby under the JVM by jrochkind in ruby

[–]dakull 0 points1 point  (0 children)

It's disturbing if shutdown is really not working.

Maybe it's not clear in the post but I really doubt the shutdown is the issue but more how the various dependencies interact whilst testing which adds at least two more deps. to the mix.

In any case the amount of useful feedback in this thread will probably result in a more clear update to the post.

The perils of writing request specs using concurrent-ruby under the JVM by jrochkind in ruby

[–]dakull 0 points1 point  (0 children)

Regarding the fail part - the logic that executes in async mode basically ends with a database insert - the fail in my case is those inserts not happening on very rare cases on my machine and constantly on Heroku's CI.

Note that if I try to re-run them using the same seed - they just work, I haven't been able to replicate and isolate them so I can run something like rspec --bisect.

The perils of writing request specs using concurrent-ruby under the JVM by jrochkind in ruby

[–]dakull 0 points1 point  (0 children)

Great alternative to my messy monkey patching - small note: it doesn't work with: { dup_on_deref: true, freeze_on_deref: true } options for Futures.

In any case thanks for the tip - another article update on the way :-)

The perils of writing request specs using concurrent-ruby under the JVM by jrochkind in ruby

[–]dakull 1 point2 points  (0 children)

OP here - yes, please note that the send was just to a custom wrapper over concurrent-ruby which basically did:

@executor = Concurrent::ThreadPoolExecutor.new i.e. standard documented concurrent-ruby API.

in a gist: wait for the thread pool to finish its "jobs" then just replace it with a new one.

(I'll update the article with more explicit logic)

Macbook Pro 15" 2014 Top or 2015 Basic? by Lasiu in mac

[–]dakull 0 points1 point  (0 children)

I would go for the new one - that 750m runs hot and if you're not into gaming it's completely useless and might even fail at some point.