New Xeon Computer

Mine is same as yours Austin

Where you have the issues before the update?

My routine is to run each step separately, close and re-open before the next step. Touch wood its chugging along as we speak…it hung at Calibrate with 11000 images, but now with 8500 images it completed step 1 in 24 hours. Now I am in step 2 generating the points.

The main issue for me was Step 3, load point cloud. Thats where I hold my breath each time…so far in the last few days, it has not hung.

I am running win 10 pro Version 1511 os build 10586.494 with two 970

In my opinion, all of these issue are code related. Have you noticed how step 2 doesn’t turn green even though its completed? How about the Not Responding Ā message each time you try to do something? Also occurs when loading a large project…

Its like its all held together with string! BUT…the only option is Photoscan and thats equivalent to having a root canal…I tried it. Very clunky ( the app not the root canal).

Ā 

Ā 

Philip I agree that Photoscan is clunky , but I do not have these issues with my pix4d.

Arturo,

What version/build of Windows are you running?

I am running win 10 pro Version 1511 os build 10586.494 with two 970

Way back at the beginning of the thread there are basic specs for one of my workstations, an HP Z800 running an older generation of dual Xeon processors on Win 7 64-bit. It is a very robust machine but I migrated Pix4D to a cheap computer I built. The homebuilt machine is much much faster. I don’t think the issue has to do with Windows 10 or the latest generation of Xeon processors. I think maybe just the Xeon in general. But I don’t wish to speculate too much.

Steven, what specs are the homemade machine?

Pix4D have suggested the following until they resolve:

Ā 

  • Update motherboard BIOS

  • Update chipset driver

  • Disable hyperthreading

  • Update Quadro driver (crucial)

And incase you didnt see this:Ā https://support.pix4d.com/hc/en-us/articles/210951143-Long-processing-time-with-Xeon-v3-processors#gsc.tab=0

Ā Also - I have been reading about PCIe optimisation and it might be helpful for some of you. Heres the HP related doc but I am sure the fundamentals are true for all systems:

http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA5-4045ENW.pdf

Lastly - I was reading a forum article where a user had a dual Xeon but had not filled up all of the memory DIMM slots, therefore forcing the CPU’s to fight for a reduced amount of physical memory access. Its important to have all slots filled for each CPU.

Arturo, the specs of the machine are in a few of the comments on the bottom of the first page of this thread. I don’t want anyone thinking it is the perfect machine built by an expert. It was an exercise for me toĀ see how much faster I could make a machine using inexpensive components with modern architecture. That being said, it’s pretty quick.

I used an eight-core AMD FX-8370 over-clocked to a conservative 4.5Ghz, two Samsung 950 Pro M.2 directly into PCIe, one for operating system and one for data, and a third Samsung 850 Pro through conventional SATA for other data. Only 16Gb of fast RAM and an NVIDIA GTX760 2GB.

The AMD processor was very inexpensive. If I had built the same system with the latest Intel processor and a much more expensive video card it would have been quicker but cost four times as much.

Also, Jerry Balch describes a ā€˜gaming’ build in the first pages of this thread versus a workstation.

Ā 

Philip enclosed a link to the HP Z840 white paper. Each HP machine I have seen with a Xeon processor has a table and loading order to fill the DIMM sockets with memory. My understanding continues to be that not that every slot needed to be filled, but the manner in which they were filled needed to follow the guidelines.

Ā 

Ā 

Ā 

Very buggy software. I just had P4D hang on an i7 during stage 2, Poisson Reconstruction. It sat there at zero percent, full CPU for 8 hours. I killed it, reopened and stage 2 had completed despite saying zero.

Anyway, this was on an i7, not a Xeon and latest Win 10.

Philip I thought of something, but you have probably already thought of it as well. I’ve been working with Pix4D now for several years and as such software goes have found it to have advanced in features quickly while remaining remarkably stable. There are still functions I’d like it to have that are lacking, but the overall experience has been that the software is solid. I think Arturo has said something similar?

What I have noticed however, is a recent software addition to my computer which performs image manipulation and measurement can crash Pix4D. This program is very lightweight and not particularly graphics intensive, but if I work with it while Pix4D is running I can risk crashing Pix4D with some regularity.

I also have NVDIA’s stereo setup on the machine which I avoid while processing, butĀ I’ve seen a program trigger the emitter that isn’t even stereo.

I’m guessing you’re probably leaving your processing machine sit idle with nothing else running(?) but just in case you’re not I wanted to report my experience.

Hi Steven - you are right, I don’t breathe near it incase it goes into one of its Program Not Responding panics…

So last night, my 8500 image dataset hung on step 3, Load Point Cloud. I killed it, restarted and it managed to squeak past it and complete that stage…currently its making the ortho so I might actually complete!

Whats weird is that it raced to 82% in a few mins and then took 12 hours to complete that remaining 18%…why would that be?

This is on the dual Xeon.

The i7 Bootcamp/iMac/Win 10 machine is chugging along without much ado on a 5000 image dataset.

I actually tried disabling hyper threading on the Xeon and it wouldn’t even load the project…

No word out of P4D support today - I might send in a summary of my findings.

I really hope that we will look back on these issues as a ā€˜remember when…’…

Ā 

Ā 

Ā 

Ā 

2.2 is out…lets see if Xeons work properly!

Processed 2315 photo project with 2.2 in 12 hours 52 min.Ā 

System is Dual Xeon E5-2687W v3

ASUS Z10PE-D8 WS motherboard

64gb ECC memory

1.2tb intel 750 PCi SSD

2 NVIDIA GeForce GTX 970 in SLI

Ā 

Austin - I am not sure if thats fast or slow! How was the Load Point Cloud part for you? My last project it was really fast to 72% then took hours to complete the remaining…

I was talking to some friends who work in a high data processing environment for geophysical data - one of the advantages they have over thier competitors is that the software is written specifically to harness the power of the hardware and therefore is much faster…

We need to see an Intel Xeon optimised version of Pix4D Mapper Pro. I have asked several times but not had any definite answers.

Ā 

last time I processed this project with a single GTX 970 and the older version of Pix it took 14 hours 40 min.

Ā