[Bug]: RAM 99%, DB no saving data and not possible to open cfg about openbullet2 HOT 4 OPEN

2. 40-90k + custom 100-700k

You're getting that many hits per minute? How is it possible with 1200-2000 CPM? Anyways, OB2 is not built to handle this kind of throughput. I suggest you:

* disable the database hit output and only use the file system one

* decrease the number of bots and see if you can get the same CPM with half the bots or so

Please let me know if it's better.

I have in mind to change the writes of hits to the database by using raw queries, so I will leave this issue open to track this.

Yea, this point is solve my issue
"disable the database hit output and only use the file system one"

from openbullet2.

You can remove the "Database" hit output and only leave the "File system" hit output in your job options, so that it will not save hits to the database but only to file.

Also, a few more questions please

1. how would you define "big amount of word list"? How many wordlists and how many lines?
2. do you get a huge number of hits? how many per minute?
3. how many bots do you use?
4. what's the CPM?

from openbullet2.

You can remove the "Database" hit output and only leave the "File system" hit output in your job options, so that it will not save hits to the database but only to file.

Also, a few more questions please

1. how would you define "big amount of word list"? How many wordlists and how many lines?

2. do you get a huge number of hits? how many per minute?

3. how many bots do you use?

4. what's the CPM?

1.2,500000 lines
2. 40-90k + custom 100-700k
3. 200
4. 1200-2000

from openbullet2.

2. 40-90k + custom 100-700k

You're getting that many hits per minute? How is it possible with 1200-2000 CPM?
Anyways, OB2 is not built to handle this kind of throughput. I suggest you:

• disable the database hit output and only use the file system one
• decrease the number of bots and see if you can get the same CPM with half the bots or so

Please let me know if it's better.

I agree that the native client has a problem of concurrency where the collection of hits can be modified while it's being enumerated, and I will address that.

from openbullet2.