You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I've been helped by @fommil the last few days profiling and benchmarking Magnolia. And I'm very happy with the results for a variety of different kinds of JSON en/decoder derivations. The bottom line is, in all tests Magnolia is now between parity and 50% faster than shapeless!pic.twitter.com/OGOrZfvvYw
The benchmarks don't tell the full story, of course. Part of the work involved removing unnecessary allocations in Magnolia, but some was in changing the APIs to facilitate writing derivations in more performant ways. Releasing Mercator this morning was a side-effect of that.
But I'm at the stage now where the overhead of Magnolia is negligible, and the typeclass instances it's deriving are close to what manually-derived instances would be. I still have a couple of newly-introduced bugs to fix but should release this perf boost by the end of the week.
I'll be interested to see how they compare once 2.13.0-M5 is out.
Yeah, we should do that. I'm also trusting that @fommil's shapeless derivations aren't too heavy on Thread.sleeps.
just curious if what you’re doing could just make shapeless faster. why something else?
It's a completely different approach to shapeless, so there's basically no opportunity to improve shapeless with ideas from Magnolia. Magnolia is only a 95% solution in turns terms of supported derivations. There's more information on the website at http://magnolia.work .
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
