You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to COLMAP
Hi,
I'm looking into ways to accelerate the dense_stereo stage. I can start looking into multi-gpu solutions, but I noticed that colmap takes <1gb on my gpu, so I was wondering if there was anyway to allow it to parallelize further on the single gpu case.
Johannes Schönberger
unread,
May 2, 2017, 12:46:16 PM5/2/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to COLMAP, siddarth...@gmail.com
There shouldn't be a benefit in running multiple tasks on the same GPU. But you can already do that now by simply passing the same GPU index multiple times to the ``--DenseStereo.gpu_index``. COLMAP also automatically uses multiple GPUs. Please refer to https://colmap.github.io/faq.html#multi-gpu-support-in-dense-reconstruction.
s...@hivemapper.com
unread,
May 8, 2017, 7:47:23 PM5/8/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to COLMAP, siddarth...@gmail.com
Yes there doesn't seem to be any benefit. To be more specific, I was wondering if there was something analogous to increasing the block size in the feature matching stage ie. use more gpu memory to save on processing time if there was some hard-coded limit on how much gpu memory one could use. I am guessing that the bottleneck is somewhere else though.