[pdal] PDAL decrease performance after hardware change

[Howard Butler]

On May 6, 2014, at 9:53 AM, Oscar Martinez Rubi <O.MartinezRubi at tudelft.nl> wrote:

> Hi guys,
> 
> I have two problems that are driving me quite crazy. The first one is related to compilation of PDAL:

> /home/oscar/sw/PDAL/src/../include/pdal/IStream.hpp: In member function ‘std::istream* pdal::IStream::popStream()’:
> /home/oscar/sw/PDAL/src/../include/pdal/IStream.hpp:78: error: ‘nullptr’ was not declared in this scope

We have been stretching things out recently, and and PDAL probably requires a gcc 4.6 or clang 3.4+ on linux for now. I expect that we will back off of that to something approaching gcc 4.6 to get many, but not necessarily all, C++11 features

> I also tried without embed boost but also crashed.
> 
> It compiles fine if I use the tag 0.9.8 though. I do not know if anybody else is having this issue or whether you are already aware of this (if that is the case I am sorry!)

Try a sha somewhere about a02bca202afcb26ea694c8f864d292794944dadd or thereabouts near the end of February. At that time is when some of the C++11 features started creeping in.


> I also tried the PDAL in https://github.com/pramsey/PDAL/ since I want to use PDAL for pointcloud in postgres (actually what is the difference between the two repositories?). In this one I manage to compile the latest but I always get the error Caught PDAL exception: drivers.pgpointcloud.writer num_points > m_patch_capacity! when loading files.

> 
> If I use a previous version of the code in the pramsey repository, for example revision 50ed6d4 (git reset --hard 50ed6d4) then it works fine.
> 
> Any help?
> 
> The second problem I have is a decrease of PDAL performance after a hardware/software change on my main testing server.

The first thing to check is your CMAKE_BUILD_TYPE configuration. If it is Debug instead of Release, you will see at least a 2x performance penalty. That would be the first thing to check. The second thing to check is the configuration of your filters.cache in your pipeline. You want its options to be only

>    <Filter type="filters.cache">
>                 <Option name="max_cache_blocks">1</Option> 

> Thanks a lot in advance and sorry for long mail!

Good luck, and please report back if you continue to have trouble.

Howard