hyperia | forem | |
---|---|---|
1 | 198 | |
44 | 21,573 | |
- | 0.3% | |
3.2 | 9.8 | |
about 3 years ago | 7 days ago | |
Zig | Ruby | |
MIT License | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hyperia
-
Lock-free, allocation-free, efficient thread pool
This actually can be at the level of a missed optimization. A run queue with a lock-shared queue amongs all the threads scales even worse than the tokio version. Sharding the run queues and changing the notification algorithm, even while keeping locks on the sharded queues improves throughput drastically.
Tokio is an async runtime, but I don't see why being an async runtime should make it worse from a throughput perspective for a thread pool. I actually started on a Rust version [0] to test out this theory of whether async-rust was the culprit, but realized that I was being nerd-sniped [1] at this point and I should continue my Zig work instead. If you're still interested, I'm open to receiving PRs and questions on that if you want to see that in action.
It's still correct to benchmark and compare tokio here given the scheduler I was designing was mean to be used with async tasks: a bunch of concurrent and small-executing work units. I mention this in the second paragraph of "Why Build Your Own?".
The thread pool in the post is meant to be used to distribute I/O bound work. A friend of mine hooked up cross-platform I/O abstractions to the thread pool [2], benchmarked it against tokio to be have greater throughput and slightly worse tail latency under a local load [3]. The thread pool serves it's purpose and the quicksort benchmark is to show how schedulers behave under relatively concurrent work-loads. I could've used a benchmark with smaller tasks than the cpu-bound partition()/insertion_sort() but this worked as a common example.
I've already mentioned why rayon isn't a good comparison: 1. It doesn't support async root concurrency. 2. scoped() waits for tasks to complete by either blocking the OS thread or using similar inline-scheduler-loop optimizations. This risks stack overflow and isn't available as a use case in other async runtimes due to primarily being a fork-join optimization.
[0]: https://github.com/kprotty/zap/blob/blog-rust/src/thread_poo...
[1]: https://xkcd.com/356/
[2]: https://github.com/lithdew/hyperia
[3]: https://gist.github.com/kprotty/5a41e9612657de00788478a7dde4...
forem
-
Deploying Forem on Render.com PromptZone.com
The journey of deploying an open-source software platform like forem can be complex and daunting, but with the right tools and services, it can also be remarkably rewarding. This article details my experience deploying Forem, the software behind the Dev.to, on Render.com, deploying Promptzone.com.
-
Lesser Known Features of DEV β Embeds!
In the future, I think we will probs make this uniform with the others. I've logged this request here on GitHub... hmmm, maybe I should embed it here instead. π
-
I fixed the "Save draft" Button on dev.to - No Accidental Publishing Anymore π
I even opened a discussion, which got no responses so far (which I think existed somewhere else or I am the only one with this issue...).
-
What are you learning about this weekend? π§
Whether you're sharpening your JS skills, making PRs to your OSS repo of choice π, sprucing up your portfolio, or writing a new post here on DEV, we'd like to hear about it.
-
Tackling Clickbait on DEV: Strategy and Technical Approach
Add articles clickbait_score as factor in final feed ordering #20493
-
Crushing it: My New Year's Resolutions for 2024
Do more documentation-related and code contributions to Forem's repository
-
πΊπΌ My life update and the Open Source #DEVImpact2023
This year again, I contributed to DEV with multiples ways, I've contributed very little to the repository, moderated the bad posts quite a bit, and welcomed newcomers to the platform. I feel that a place like this should always be so welcoming to users, so why shouldn't I?
-
π #DEVImpact2023: A Year of Challenges, Triumphs, and The Future
docs: making updates to Editor Guide #20258
-
Open Source alternatives to tools you Pay for
Forem - Open Source Alternative to Circle
-
What you learning about this weekend? π§
Whether you're sharpening your JS skills, making PRs to your OSS repo of choice π, sprucing up your portfolio, or writing a new post here on DEV, we'd like to hear about it.
What are some alternatives?
zap - An asynchronous runtime with a focus on performance and resource efficiency.
Discourse - A platform for community discussion. Free, open, simple.
OSStreams - Open-source, Cloud-native Streams
ComfyJS - Comfiest Twitch Chat Library for JavaScript | NodeJS + Browser Support
klipse - Klipse is a JavaScript plugin for embedding interactive code snippets in tech blogs.
reactor - Phoenix LiveView but for Django
ghost-on-heroku - One-button Heroku deploy for the Ghost 3.2.0 blogging platform.
Ruby on Rails - Ruby on Rails
Puma - A Ruby/Rack web server built for parallelism
Hacktoberfest2023 - About Make your Pull Request on Hacktoberfest 2023. Don't forget to spread love and if you like give us a βοΈ
cypress-rails - Helps you write Cypress tests of your Rails app