DEV Community

loading...
Cover image for Monitoring and Performance Wrap Up - June 2020
Raygun

Monitoring and Performance Wrap Up - June 2020

raygun_staff profile image Raygun Staff Updated on ・2 min read

Hi! I'm Helen, one of your friendly mods looking after the #monitoring and #performance tags.

At the end of each month, I'll be showcasing some of the great posts, projects, and insights from the Dev community.


Kicking us off this month is Abdisalan, who makes the case that offset has its place, but not as a tool for pagination. Check out the post and comments for more efficient alternatives.



Ivo then makes a case for moving away from OFFSET and LIMIT when building reliable systems. If you are struggling with performance check out the advice to ensure your server can store data in memory and paginate effectively.



Next, Rhymes and Molly from the Dev team share how they used jemalloc when facing memory troubles. This alternative memory allocator can be used by multithreaded Ruby apps, like Dev.to



We then move on to JavaScript, I/O operations, and CPU-intensive tasks. By understanding their use cases, one can confidently identify the correct tools for maximizing JavaScript concurrency.



Our next post from the Linkurious team details how they decided to give WASM a try and run a thorough benchmarking project before jumping on the bandwagon.



Our next post from Trishul gives an introduction on web workers. Check it out for more on how to use them for CPU intensive operations while the UI is free and responsive.



To finish up we have a post from Bruno who takes on performance issues with Bullet. It’s very difficult to catch every N + 1 in every query we build and it’s even harder to detect cases where we should no longer preload data.



That's all for this month! For more, check out the #monitoring and #performance tags.


Discussion (0)

Forem Open with the Forem app