[SERVER-34562] I use YCSB testing comparise mongodb3.6.3 with mongodb3.4.13 ,find the mongodb3.4.13 insert and update performance is one and a half times than mongodb3.6.3 Created: 19/Apr/18  Updated: 05/Dec/18  Resolved: 05/Dec/18

Status: Closed
Project: Core Server
Component/s: Performance
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: hancang2000 Assignee: Kelsey Schubert
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-31694 17% throughput regression in insert w... Closed
is related to SERVER-34604 low performance under 3.6.4 with wire... Closed
Participants:
Linked BF Score: 0

 Description   

ycsb configuration

#recordcount=100000000
recordcount=100000000
#operationcount=100000000
operationcount=100000000
workload=com.yahoo.ycsb.workloads.CoreWorkload
threadcount = 50

readallfields=true

readproportion=0
updateproportion=0
scanproportion=0
insertproportion=1
readmodifywriteproportion=0

requestdistribution=zipfian
insertorder = hashed
readallfields=true
fieldlength = 200
fieldcount = 10
#mongodb.writeConcern = majority
mongodb.writeConcern = acknowledged
mongodb.database = ycsb

mongodb3.6.3

mongodb3.6.3 networkMessageCompressors use disabled or use ,the performace low many than mongodb3.4.13

configuration

dbpath=/home/data/mongodb/db

#where to log
#logpath=/home/***/log/mongodb/mongodb.log
syslog=true
logappend=true

bind_ip_all = true
port = 27017

  1. Enables periodic logging of CPU utilization and I/O wait
    cpu = true
  1. Turn on/off security. Off is currently the default
    #noauth = true
    auth = true

keyFile = /home/***/conf/mongodb/keyfile

  1. Disable the HTTP interface (Defaults to localhost:27018).
  1. in replica set configuration, specify the name of the replica set
    replSet = ***
  1. max connections
    maxConns = 65535

#profile=1
#slowms=1000
smallfiles = true
noprealloc = true
#noMoveParanoia = true
#syncdelay=600
oplogSize = 20000
wiredTigerDirectoryForIndexes = true
directoryperdb = true
wiredTigerCacheSizeGB = 16
shardsvr = true
storageEngine = wiredTiger
networkMessageCompressors = disabled



 Comments   
Comment by Kelsey Schubert [ 06/Nov/18 ]

Hi cristian.vertiz@mojix.com,

The fixes that we've seen show the most significant improvements in our testing are WT-4111 and WT-4125. These are currently available in the recent 4.0 releases and will be included in the upcoming release of the 3.6 branch, MongoDB 3.6.9.

Kind regards,
Kelsey

Comment by Cristian Manuel Vertiz Fernandez [ 27/Sep/18 ]

Hi @kelsey.schubert 

Are those fixes going to be included in next mongodb 4.0.x stable release?

Comment by Kelsey Schubert [ 27/Sep/18 ]

Hi zhouhancang,

A number of fixes have gone into the server to address the regressions our internal testing has identified. However, we still observe an 10-20% regression since 3.4. Would you please rerun your experiment on the latest version of MongoDB 3.6, and let us know if you see similar improvement? Currently, we are prioritizing performance work in other areas and do not have additional improvements planned for this issue. However, if your tests do not show improvement, we'll continue to investigate possible explanations for this disparity.

Thank you,
Kelsey

Comment by David Daly [ 02/May/18 ]

I've linked this ticket to related tickets we're investigating. The internal investigation tickets won't be visible to external users, but they are there. 

Comment by Kelsey Schubert [ 01/May/18 ]

Hi zhouhancang,

Thank for reporting this issue. Our internal automated performance testing has identified some regressions which may be related to the performance that you're observing in your tests. To most effectively work to improve performance, we're focusing on our investigation against our internal performance benchmarks which are configured to be consistent and stress particular mongod access paths. Once these issues have been resolved, we may be able to revisit this issue to see whether the same fixes resolve this particular performance regression.

Kind regards,
Kelsey

Comment by hancang2000 [ 19/Apr/18 ]

mongodb3.4.13 ycsb performance

[OVERALL], RunTime(ms), 5246888.0
[OVERALL], Throughput(ops/sec), 19058.91644723501
[TOTAL_GCS_PS_Scavenge], Count, 14572.0
[TOTAL_GC_TIME_PS_Scavenge], Time(ms), 42861.0
[TOTAL_GC_TIME_%_PS_Scavenge], Time(%), 0.8168842178449397
[TOTAL_GCS_PS_MarkSweep], Count, 4.0
[TOTAL_GC_TIME_PS_MarkSweep], Time(ms), 219.0
[TOTAL_GC_TIME_%_PS_MarkSweep], Time(%), 0.004173902701944466
[TOTAL_GCs], Count, 14576.0
[TOTAL_GC_TIME], Time(ms), 43080.0
[TOTAL_GC_TIME_%], Time(%), 0.8210581205468841
[CLEANUP], Operations, 50.0
[CLEANUP], AverageLatency(us), 906.68
[CLEANUP], MinLatency(us), 1.0
[CLEANUP], MaxLatency(us), 45215.0
[CLEANUP], 95thPercentileLatency(us), 8.0
[CLEANUP], 99thPercentileLatency(us), 45215.0
[INSERT], Operations, 1.0E8
[INSERT], AverageLatency(us), 2611.9168896
[INSERT], MinLatency(us), 580.0
[INSERT], MaxLatency(us), 5189631.0
[INSERT], 95thPercentileLatency(us), 4503.0
[INSERT], 99thPercentileLatency(us), 12775.0
[INSERT], Return=OK, 100000000

mongodb3.6.3 ycsb performance
[OVERALL], RunTime(ms), 8196936.0
[OVERALL], Throughput(ops/sec), 12199.680465969235
[TOTAL_GCS_PS_Scavenge], Count, 24830.0
[TOTAL_GC_TIME_PS_Scavenge], Time(ms), 63666.0
[TOTAL_GC_TIME_%_PS_Scavenge], Time(%), 0.7767048565463974
[TOTAL_GCS_PS_MarkSweep], Count, 10.0
[TOTAL_GC_TIME_PS_MarkSweep], Time(ms), 333.0
[TOTAL_GC_TIME_%_PS_MarkSweep], Time(%), 0.004062493595167756
[TOTAL_GCs], Count, 24840.0
[TOTAL_GC_TIME], Time(ms), 63999.0
[TOTAL_GC_TIME_%], Time(%), 0.7807673501415651
[CLEANUP], Operations, 50.0
[CLEANUP], AverageLatency(us), 969.5
[CLEANUP], MinLatency(us), 2.0
[CLEANUP], MaxLatency(us), 48351.0
[CLEANUP], 95thPercentileLatency(us), 13.0
[CLEANUP], 99thPercentileLatency(us), 48351.0
[INSERT], Operations, 1.0E8
[INSERT], AverageLatency(us), 4083.44117683
[INSERT], MinLatency(us), 765.0
[INSERT], MaxLatency(us), 1.2320767E7
[INSERT], 95thPercentileLatency(us), 6879.0
[INSERT], 99thPercentileLatency(us), 22863.0
[INSERT], Return=OK, 100000000

Generated at Thu Feb 08 04:37:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.