Local development: Uploading large number of input cases times out web ui for some time about clusterfuzz HOT 8 CLOSED

After the bot finished update cases, the error messages stop and the web ui becomes functional again.

from clusterfuzz.

How big was testcase archive ? what is average size for testcase. Note that local development scenario is not recommended for large scale tests. Recommended to do production setup for these.

from clusterfuzz.

all test cases are less than 30 bytes.

from clusterfuzz.

The zip file is about 4mb.

from clusterfuzz.

How long was the web ui inaccessible for ? > 1min ? this shouldn't happen again as this step was more about unpacking testcases quickly and storing them in db. we can add a throttle, but unsure if it is worth it in unpack_task. can you try a time.sleep there and maybe try a PR.

from clusterfuzz.

the web ui is inaccessible for more than 5 minutes.
BTW, I just realized the primary usage of "upload testcase" is for bad cases like crashes, not for seed.
So I think I used this feature incorrectly.

In other words, I feel uploading lots of cases is unusual and thus this issue is not important (given it's local only). So you are free to close this issue.
OTOH, revising doc or ui to indicate "bad testcase" might be a good idea. Anyway, up to you.

from clusterfuzz.

anyone can use it to upload thousands of crashes for analysis. so, we can see and make a simple throttle in unpack_task.

from clusterfuzz.

yes throttling is not a good idea, considering this works perfectly in prod environment and has been tried multiple times by other Googlers. For local environment, i dont see a usecase to upload thousands, maybe someone need 1 or <10-50.

from clusterfuzz.