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

batch process will use so many cpu and memory , the computer is stuck. can optimize the performance ,gobuster scan is use a litttle cpu and memory #1007

Closed
fayewong00 opened this issue Dec 28, 2021 · 7 comments · Fixed by #1395
Labels
enhancement New feature or request help wanted Extra attention is needed Priority: High

Comments

@fayewong00
Copy link

batch process will use so many cpu and memory , the computer is stuck. can optimize the performance ,gobuster scan is use a litttle cpu and memory.gobuster is use golang.

@fayewong00 fayewong00 added the question Further information is requested label Dec 28, 2021
@shelld3v
Copy link
Collaborator

You can reduce the threads

@fayewong00
Copy link
Author

You can reduce the threads

so many webs penetration testing ,batch

@shelld3v
Copy link
Collaborator

shelld3v commented Jan 8, 2022

I don't understand what do you mean

@fayewong00
Copy link
Author

fayewong00 commented Jan 9, 2022

I don't understand what do you mean

With a small amount of testing, the tool is fine. But batch testing will consume a lot of computer resources, causing the computer to freeze. Usually batch testing is very much, reducing the number of threads will not solve the problem. Gobuster runs the same tasks with very few resources, a little CPU and memory! Can performance be improved!

@shelld3v
Copy link
Collaborator

shelld3v commented Jan 9, 2022

I will try to figure out how to improve dirsearch performance, but this seems to be a long-term issue, might take a lot of time and can not be fully fixed

@shelld3v shelld3v added enhancement New feature or request Priority: Medium and removed question Further information is requested labels Jan 9, 2022
@fayewong00
Copy link
Author

I will try to figure out how to improve dirsearch performance, but this seems to be a long-term issue, might take a lot of time and can not be fully fixed

Thank you very much! Found in batch test process, occupy computer resources too much, so make a suggestion! I also know that this is a long and arduous task. If you have time, you can try to improve the performance. If you don't have time, you can do it temporarily. Multithreaded coroutine concurrency, occupying resources, Golang language shows natural superiority! Python is also great, but less performance wise!

@shelld3v shelld3v added help wanted Extra attention is needed Priority: Critical and removed Priority: Medium labels Jul 29, 2022
Repository owner deleted a comment from guendouzaimed Apr 8, 2023
@zrquan
Copy link
Contributor

zrquan commented Oct 13, 2024

Dirsearch can now enable asynchronous mode with --async, which should help improve this issue. Feel free to try it and provide feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed Priority: High
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants