You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested the "ipfs add" performance in a high concurrency scenario on my centOS node environment
When my IPFS repo storage and files over a huge amount(30G+), "ipfs add" action slow down ,Surprisingly,I simulated 100 processes work on it at the same time,and it's cost morn than 10 seconds ,and I adjusted the process to 1000,it cost almost 2 mins 。
"real 0m9.627s
user 0m0.077s
sys 0m0.017s
real 0m9.634s
user 0m0.089s
sys 0m0.007s
real 0m9.826s
user 0m0.083s
sys 0m0.019s
real 0m9.784s
user 0m0.090s
sys 0m0.013s
real 0m9.949s
user 0m0.089s
sys 0m0.011s
real 0m10.046s
user 0m0.089s
sys 0m0.017s
real 0m10.108s
user 0m0.102s
sys 0m0.012s
real 0m10.383s
user 0m0.084s
sys 0m0.017s
real 0m10.530s
user 0m0.105s
sys 0m0.015s
real 0m10.527s
user 0m0.080s
sys 0m0.017s
time-consuming: 12 seconds
The cause of the problem, I guess, may be due to the seriousness of the Merkle tree's shard retrieval, Is official team encountered this problem? What is the reason of this issue? Can I help you optimize this issue together?
The text was updated successfully, but these errors were encountered:
Is this a feature of an experiment used to replace level-DB?I will take the time to find out badget KV DB and I will also think about whether there is a better optimization plan for this issue and submit it to you.
Version information:
go-ipfs version: 0.4.17-
Repo version: 7
System version: amd64/linux
Golang version: go1.10.3
Type:
Bug, Feature
Description:
I tested the "ipfs add" performance in a high concurrency scenario on my centOS node environment
When my IPFS repo storage and files over a huge amount(30G+), "ipfs add" action slow down ,Surprisingly,I simulated 100 processes work on it at the same time,and it's cost morn than 10 seconds ,and I adjusted the process to 1000,it cost almost 2 mins 。
This is our test shell script:
This is result of time consuming:
The cause of the problem, I guess, may be due to the seriousness of the Merkle tree's shard retrieval, Is official team encountered this problem? What is the reason of this issue? Can I help you optimize this issue together?
The text was updated successfully, but these errors were encountered: