Doubt meaning "return = 1" #314
Comments
|
For the MongoDB client it means that the operation did not complete successfully. For a read that means the document we are searching for was not found. For an insert or update it means the operation failed. Can you give more details on:
Thanks, |
|
The MongoDB Version 1:2.0.6-1.1 configuration default, no modified. 100% insert does not display error Hardware 2Core processor 2GB RAM Command line: -db com.yahoo.ycsb.db.MongoDbClient -p mongodb.url=mongodb://ip/27017 -p mongodb.database=ycsb -p mongodb.writeConcern=normal -threads 10 -P /YCSB/workloads/workload_update_10000 -s -t |
|
Would you mind posting the modified workloada? Can you tell me the version of YCSB? Have you tried the master branch? Just to confirm you ran the ycsb load prior to the actual run correct? I have recently seen some |
|
please try with the current release candidate from #266 rather than the On Thu, Jun 25, 2015 at 6:36 PM, allanbank notifications@github.com wrote:
Sean |
|
Yes I ran the load prior Workload modified Copyright (c) 2010 Yahoo! Inc. All rights reserved.Licensed under the Apache License, Version 2.0 (the "License"); youmay not use this file except in compliance with the License. Youmay obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing, softwaredistributed under the License is distributed on an "AS IS" BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express orimplied. See the License for the specific language governingpermissions and limitations under the License. See accompanyingLICENSE file. # Yahoo! Cloud System BenchmarkWorkload A: Update heavy workloadApplication example: Session store recording recent actionsRead :1Default data size: 1 KB records (10 fields, 100 bytes each, plus key)Request distribution: zipfianrecordcount=10000 Copyright (c) 2010 Yahoo! Inc. All rights reserved.Licensed under the Apache License, Version 2.0 (the "License"); youmay not use this file except in compliance with the License. Youmay obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing, softwaredistributed under the License is distributed on an "AS IS" BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express orimplied. See the License for the specific language governingpermissions and limitations under the License. See accompanyingLICENSE file.Yahoo! Cloud System BenchmarkWorkload A: Update heavy workloadApplication example: Session store recording recent actionsUpdate :1Default data size: 1 KB records (10 fields, 100 bytes each, plus key)Request distribution: zipfianrecordcount=10000 requestdistribution=zipfian |
|
@cgara - I have tried to reproduce the large number of non-zero return values and can't figure out what is going on. Did you have a chance to test wit a 0.2.0-RC? I did notice from your original post that the workloads are taking a lot longer for you than me. What is the ping time from your YCSB client to the MongoDB server? Thanks, P.S. FYI - I am pretty sure that the small numbers of non-zero returns for workloadd are caused by #327. |
|
the return 1 changes the result of runtime? I not tested the 0.2.0-RC. Actually performed these workloads to two DBMS is only mongo showed return 1. I will measure the ping and inform you. Thanks, |
|
PING 192.168.0.104 (192.168.0.104) 56(84) bytes of data. |
|
Those ping times explain the lower throughput (mine are 0.1 ms to between my test machines) but not the non-zero return values. I have made a number of significant changes to the MongoDB client for YCSB over the last few months including making sure that the return values mean something for each operation. I can tell from the output you posted that the version of YCSB you are using is older than those changes. If you can test with the 0.2.0-RC3 release or even the current master I suspect the non-zero return values will disappear. Rob. |
|
0.2.0 has a release now: https://github.com/brianfrankcooper/YCSB/releases/tag/0.2.0 If it makes things easier, that means you could grab the convenience binary specific to mongodb: https://github.com/brianfrankcooper/YCSB/releases/download/0.2.0/ycsb-mongodb-binding-0.2.0.tar.gz |
|
This new version 0.2.0-RC3 showed no return 1. I'm testing three DBMS, Redis, MongoDB and Cassandra, now each DBMS is with a version of ycsb, this hinders trust the results? Thanks |
|
When you say runtime values are you referring to the average latency of the requests or the wall-clock time for running the YCSB command? I would not expect the latency for each operation to have changed very much but if you can provide details on which operation and what you saw before and now I will have a look. The wall-clock time for short runs (a few 10's of seconds) is probably #316. Rob. |
|
before: [UPDATE], Return=1, 8254now: |
|
Right - That "[OVERALL], RunTime" delta is the ~20 second time I saw added to the wall clock time for #316. The problem is that instead of triggering the status thread to exit as soon as the operations complete the application is waiting for the status thread to wake up on its own and then exit. If you look further down in the new results you should find the [UPDATE] throughput and latency numbers. For MongoDB the CLEANUP is the time it takes to close the MongoClient. Only the last CLEANUP actually does the close operation which is why the MinLatency is 4 us and the max is 46 ms. Rob. |
|
Did all your questions get answered @cgara? |
|
Yes, all questions were answered. I am performing exautivos tests with the tool, and I wonder if the runtime takes into account also the connection and disconnection time with the DBMS |
|
I believe that gets covered in the startup and cleanup times. |
Hi,
The "return = 1" means response to the absence crud operation or error in crud operation?
In mongodb it is happening error by twenty percent of the procedure. I disregard the results?
Thank you
The text was updated successfully, but these errors were encountered: