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

Modlog casesfor #2964

Closed
SharkyTheKing opened this issue Aug 29, 2019 · 1 comment · Fixed by #3075
Closed

Modlog casesfor #2964

SharkyTheKing opened this issue Aug 29, 2019 · 1 comment · Fixed by #3075
Assignees
Labels
Status: Needs Info

Comments

@SharkyTheKing
Copy link
Contributor

@SharkyTheKing SharkyTheKing commented Aug 29, 2019

Other bugs

What were you trying to do?

For each modlog cases that are created, it's sent to the file or so that contains all the modlog information. So, while doing the [p]casesfor command. When you have a large (currently our modlog case is around 68k, almost 69k) number of cases every time you do the casesfor it takes longer compared to someone who wouldn't have that large amount of cases. As we continue to grow with the number of cases, expecting the command process to take longer.

What were you expecting to happen?

Essentially, possibly adjustments of modlog cases where it clusters per ID or something that'll improve the processing time.

What actually happened?

Since we have around 68k cases going onto 69k, every time we use the casesfor command, it'll take a bit to process since it needs to loop through the entire file for the specific ID that you're searching for.

How can we reproduce this issue?

Gain a large number of cases for your bot and test the casesfor command to see the speed of the process.

@mikeshardmind
Copy link
Contributor

@mikeshardmind mikeshardmind commented Aug 29, 2019

Trying to identify the actual cause with certainty as there are a couple potential candidates for the perceived slowness, and the size of the data seems unlikely to cause a noticeable slowdown here.

Which storage backend is in use?
What is the actual speed of a response here?
Does this occur only with multiple commands used in succession, or does this also happen if it is the only command to have been run within a minute?

@mikeshardmind mikeshardmind self-assigned this Aug 29, 2019
@mikeshardmind mikeshardmind added the Status: Needs Info label Aug 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Info
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants