Output doesn't seem to be using system resources correctly

Hi all (again). This is an issue I've had for a number of years, and I just haven't bothered to report it, but the large job I'm working on now has meant that this has become a real pain..

We have a Core photo log, 2 landscape photos per page to output the core photography from a table holding BItmap field types, also a Trial Pit log with 2 photos per page on "extra" pages (max of 4 photos / 2 extra pages) These both work fine, untill you try to output a whole run of core photos, or all the trial pits in one go, at which point gINT gets so far and then just sits there with the Exporting window saying "Building BH#### (log # of #)" and does nothing else untill you have to Ctrl+Alt+Dle and end process on gINT8.exe to close gINT or it comes up with the following type error message:-

"Unable to output

Cannot open database ". It may not be a database that your application recognizes, or the file may be corrupt.

Entity type Text, X=130.2875, Y=254.5588

(OutputAppLog.OutOneLog

OutputAppLog.OutputLogCurr

OutputAppLog.OutputHeadreFooter

OutputGraphicsPass2.OutputPass2

OutputGraphicsPass2.TextEntityEval

GIDSave.SaveEntity: DAO.Recordset)

OK"

Usually it just sits there and sulks. What I'm having to do is to output just a few BH worth of core photos at a time to a PDF and then keep appending to it, till I've managed to output them. Interestingly if you watch Task Manger whilst gINT is outputting, its memory usage doesn't go much over 270MB and CPU usage doesn't go much over 5%. The same happens with outputting the TP logs with photos. Our engineers can manage to output approx 10 - 14 logs (with just 2 photos on the Additional pages) on their normal PCs, and I can manage maybe 20 on my twin Xeon, 16GB Ram workstation??? It does output the PDF to the last complete BHs woth of photos.

Miles

Parents Reply Children
  • I found the temp gdw file can get too big and make an error.  If you have one very deep borehole then try the option on the output screen to define the page range, and break up the output in to batches.

    Phil Wade
    Datgel
    Bentley Channel Partner and Developer Partner
    E: phil.wade@datgel.com | T: +61 2 8202 8600 & +65 6631 9780

    Get the most out of gINT with Datgel Tools.

  • Phil, that's the point of my post (and submission to tech support) 2 reasons.

    1. Maximum file size under NTFS file system is 16TB, there's no way gINT is generating a 16TB temp file... I've got a paltry 250GB free on my C drive, plenty of space for creating a temp file way larger than gINT would generate outputting thousands of photo logs.

    2. I'm not sure it's to do with temp file size, as I think that gINT dumps the temp file to PDF (I PDF all output and print from that, if paper output is required at all) after the successful completion of each Points worth of data. I say this because gINT still manages to generate all the photo logs in the specified PDF, up to the hole where I get the error message or gINT just goes into a sulk. It would make no programming sense to generate a massive temp file, create content from it periodically but keep that content in the temp file?

    gINT is only using a tiny amount of memory (270MB ish) and very little processor power (5%) whilst generating the logs and I'm intrigued to know why it's falling over using such a small amount of resources when I've got 12 GB ram free and another 15 processor cores it's not using at all!

    I do indeed get around this by appending to the PDF with 5 or so holes worth of core photos, it's just a pain to have to do this when my PC is more than capable of outputting all of them in one go :-(