Skip to content
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

Katana high memory usage when running with high concurrency and large lists #742

Closed
Ice3man543 opened this issue Jan 23, 2024 · 2 comments · Fixed by #1107
Closed

Katana high memory usage when running with high concurrency and large lists #742

Ice3man543 opened this issue Jan 23, 2024 · 2 comments · Fixed by #1107
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed.
Milestone

Comments

@Ice3man543
Copy link
Member

Please describe your feature request:

Describe the use case of this feature:

@Ice3man543 Ice3man543 added the Type: Enhancement Most issues will probably ask for additions or changes. label Jan 23, 2024
@ca5ua1
Copy link

ca5ua1 commented Feb 23, 2024

I guess my issue is relevant to this.

When crawling pretty big gitea repository (don't ask me why), katana may take more then 1GB of RAM and 100% CPU depending on threads/concurrency settings.
That's the example for scan with more then 1GB of RAM:
katana -u 'https://gitea.com/gitea/blog' -d 2

The key here is size of repo. With larger repos it take more RAM. But my problem that I'm running with -d 2 which should crawl only one URL basically extracting URLs from it, right?!

@moscowchill
Copy link

Here also issues with large lists however I kept lower conc but the ram runs full (32gb) after a couple hundred domains

@ehsandeep ehsandeep added Status: Completed Nothing further to be done with this issue. Awaiting to be closed. and removed Type: Enhancement Most issues will probably ask for additions or changes. labels Dec 2, 2024
@ehsandeep ehsandeep linked a pull request Dec 2, 2024 that will close this issue
@ehsandeep ehsandeep added this to the katana v1.1.2 milestone Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants