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

[BUG]perdayvolume for my bundle is not correct #212

Closed
YifengMao opened this issue May 16, 2019 · 6 comments
Closed

[BUG]perdayvolume for my bundle is not correct #212

YifengMao opened this issue May 16, 2019 · 6 comments
Assignees
Labels
bug Malfunctioning Eventgen due to potential bug

Comments

@YifengMao
Copy link
Contributor

YifengMao commented May 16, 2019

Describe the bug
perdayvolume/throughput/indexed are not correct.

To Reproduce
longevity_syslog.zip
my bundle is very simple. Here's a table of result
egx cluster 3 node to send data via hec to a standalone splunk host

httpwaitresponse payloadmaxsize perdayvolum_total Throughput actual
false 256K 200 1477K/s 126G 130G
true 256K 200 1474K/s 126G 130G
true 256K 600 4054K/s 350G 355G
true 256K 900 5863K/s 504G 498G
true 256K 3000(hit bottleneck) 10907K/s 942G 1.01T

Additional context
version: 6.3.1

@YifengMao YifengMao added the bug Malfunctioning Eventgen due to potential bug label May 16, 2019
@YifengMao
Copy link
Contributor Author

2 problems here:

  • throughput is less than half of actual throughput.
  • actual throughput is greater than perdayvolume, not in a acceptable range (+/- 10%)

@arctan5x
Copy link
Contributor

Hi Yifeng, would you verify this is the latest version? Also, would you provide environment details such as which cluster, container, etc.

@li-wu
Copy link
Contributor

li-wu commented May 31, 2019

Some testing result:

  1. Setting persistentQueueSize and queueSize with 500MB to 1GB does not take effect;
  2. Using this pr fix #166 #192 does not work;

instead:
making the timer to sleep half the self.time improves the throughput. And I will try to use more exact sleep time.

@arctan5x
Copy link
Contributor

@YifengMao would this be still valid? If not, may I close it?

@li-wu
Copy link
Contributor

li-wu commented Jul 31, 2019

@arctan5x I think this is still valid and not solved. This is also related to how we are going to measure the performance of Eventgen.

@GordonWang
Copy link
Contributor

The issue is resolved. I verified in the test env.
splunk cluster: 3 indexers and 1 SH.
set the perday volume size as 1000GB.

Then, use 2 spl to check the indexed data size. The result is near 1000GB in either way. The volume size deviation is less than 1%.

Here are the screenshots.
image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Malfunctioning Eventgen due to potential bug
Projects
None yet
Development

No branches or pull requests

6 participants