Closed weiaicunzai closed 3 years ago
This is completely speculation here, but if your data is already loaded from disk, your process will be waiting on disk less, and able to keep the GPU busy. I don't think this has anything to do with lmdb.
This is completely speculation here, but if your data is already loaded from disk, your process will be waiting on disk less, and able to keep the GPU busy. I don't think this has anything to do with lmdb.
Thanks, I've rewrite a lmdb dataset class, and above situation has disappeared, seems like the old code I wrote has come performance bottleneck.
Hi, thanks for your great work, sorry to bother, I do not know if this is the right place to ask my question.
Affected Operating Systems
Affected py-lmdb Version
'1.0.0'
py-lmdb Installation Method
Using bundled or distribution-provided LMDB library?
Bundled
Distribution name and LMDB library version
(0, 9, 24)
Machine "free -m" output
e.g.
Other important machine info
Running under cgroups? Containers? Weird filesystems in use? Network filesystem? Patched kernel? ...
Describe Your Problem
I've tried to write my data into lmdb format to boost my pytorch performance, however, I've encountered a very strange situation. Here is the code snippet in my train.py:
the
nvidia-smi
command gives me around 80% GPU-Util during training, and if I do this:GPU-Util immediately boost to 97%.
I've tried to save my training data and validation data into 1 lmdb file or separately, nothing changes, is there a reason why this would happen?Why use
lmdb.open()
function twice in a process would cause this difference, is there anything I did wrong? ThanksThere is my dataset script: https://github.com/weiaicunzai/pytorch-camvid/blob/refactor/optimize_transformations/dataset/camvid.py
Now my project code is on: https://github.com/weiaicunzai/pytorch-camvid/tree/refactor/optimize_transformations. If you need. Please note it's not on the master branch Simply do
to run my code
Thanks in advance.
Describe What You Expected To Happen
Use multiple
lmdb.open()
function in one process won't effect reading speed.Describe What Happened Instead
Use multiple
lmdb.open()
function in one process affected the reading speed