Skip to content

Instructions for non rails app #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Koilanetroc opened this issue May 20, 2024 · 2 comments
Open

Instructions for non rails app #13

Koilanetroc opened this issue May 20, 2024 · 2 comments

Comments

@Koilanetroc
Copy link

I believe this tool can be used for non rails apps, such as sidekiq or long/indefinitely running rake tasks. Do you have plans for extending this tool for a more wide usage in ruby applications?

@peterzhu2118
Copy link
Member

Yes, you absolutely can use this for jobs or non-Rails apps. It can be used for and Ruby apps that have a request-like structure (systems where the application resets to a default state after doing a task). It's simple to implement, you can follow how rack_plugin.rb does it.

If you want to implement this feature for Sidekiq, you're more than welcome to submit a PR.

@mehnaz-bano
Copy link

Has anyone found a way to use Autotuner for background jobs, such as with Sidekiq or Resque?

I've been exploring ways to optimize the performance of background job processing and how we can efficiently get suggestion to fine tune memory management especially for jobs. I came across Autotuner, which seems like it could be useful for this purpose, but I haven't found clear examples or documentation for integrating it with popular background job libraries like Sidekiq or Resque.

Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants