Speed issue on new PC with 64 bit version of GlobalMapper

LogsmithLogsmith LogsmithPosts: 12Trusted User
edited May 2014 in Technical Support
I just got a new PC yesterday and have
noted some performance problems with GlobalMapper v15 on the new PC.

The new PC does not perform as well as
the old.

Old PC
Windows Business Vista SP2
Intel Core 2Quad Q8200 at 2.33Ghz
8GB memory
32 bit Op SYS

New PC
Windows 7 Pro SegP1
Intel Core i-7-4770 CPU at 3.40Ghz
32GB Memory
64-bit Op sys

GlobalMapper Version
Build 15.1.8 (b033114) is installed on
both machines
With fix referenced from this Forum
topic applied:
Script file problem with
SET_LAYER_OPTIONS


Data consists of a very large SegP1
File (about 7 million points)

Task is to load the SegP1 file, isolate
just the line endpoints, and export the endpoints to SegP1 format.


Briefly the steps are:

Load SegP1

Select only lines and edit ... move to their own layer: “Lines”

Turn off SegP1 points layer

Select all lines from the “Lines” layer

Advanced feature creation … create point features spaced along
line... sample features at endpoints only

edit … move to “endpoints” layer

advanced feature creation … create buffers.. Create 1 meter buffer
around endpoints

turn original “SegP1” points layer back on

advanced selection … select all points within selected areas

edit … move to new “SegP1 endpoints” layer

delete unwanted points on the “SegP1 endpoints” layer( there are
original SegP1 stations, and the line “endpoints” layer points,
that were inside the buffers, delete the unwanted line“endpoints”)

Export to SegP1

The entire process is slow. But where it really suffers is at this
step:

Advanced
feature creation … create point features spaced along
line... sample features at endpoints only



During this step if I check the Windows
Task Manager I see this status:


On the Old PC GlobalMapper process is using
around 1,142,856k memory total, CPU usage is 69%

On the New PC GlobalMapper process is using
around 301,172k memory total, CPU usage is 12%


I have successfully completed this
procedure on the Old PC in about 68 min. I have yet to complete it
on the new PC.

There may be a better method by which
to do this and I'm open to suggestion if they are out there.
However, my real concern and question here is why I'm not seeing
improved performance with my new PC and the 64 bit version of
GlobalMapper? Is there anything I can do to enable GlobalMapper to
use more of the PC resources?

Comments

  • LogsmithLogsmith Logsmith Posts: 12Trusted User
    edited April 2014
    I have found part of a solution to getting this job done.
    After step "Select only lines and edit ... move to their own layer: “Lines”"

    I export the lines as a line type shape file. I then unload all. Then reload just the line shape file.
    I then rejoin my procedure above until I have created the buffers at the line endpoints.
    Then I reload the original SegP1 file and carry on with the procedure. Finding points within the selected areas (buffers), and etc.

    I was watching the windows task manager as I went and using this new procedure it does get up and use a big chunk of memory. Up to 14,000,000+ at one point. It's still a slow process. A lot of time seems to be used up by the graphics redraws. Can they be paused. I don't think so (would be a great feature). I will proceed from here now that I have a procedure and see if I can put it in a script file where I can bypass the graphics.
  • global_mapperglobal_mapper Administrator Posts: 17,238
    edited April 2014
    I have a couple of suggestions. First, since you are on 64-bit Windows get the 64-bit installer from Global Mapper Downloads. It should be much faster on 64-bit Windows. After getting that, apply the latest 64-bit build. I have placed a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper15_64bit.zip with the latest changes for you to try. Simply download that file and extract the contents into your existing v15.xx installation folder to give it a try.

    That should speed up any process, but in this case I also noticed a likely major source of slowdown in creating points from selected features. The new build should be much faster when creating a large number of points.

    Let me know if I can be of further assistance.

    Thanks,

    Mike
    Global Mapper Guru
    geohelp@bluemarblegeo.com
    Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation
  • LogsmithLogsmith Logsmith Posts: 12Trusted User
    edited May 2014
    Mike:

    Thanks for this. Yes, it is much faster.

    I noticed in my original entry above I left out 1 step to my procedure. I'll correct it here so if anyone follows in these footsteps they won't have a problem:

    Task is to load the SegP1 file, isolate just the line endpoints, and export the endpoints to SegP1 format.


    Briefly the steps are:

    Load SegP1

    Select only lines and, edit ... move to their own layer: “Lines”

    Turn off SegP1 points layer

    Select all lines from the “Lines” layer
    Crop/Combine – Resample/Split Selected Features at Specified Spacing...
    Sample features at Endpoints Only


    Advanced feature creation … create point features spaced along
    line... sample features at endpoints only

    edit … move to “endpoints” layer

    advanced feature creation … create buffers.. Create 1 meter buffer
    around endpoints

    turn original “SegP1” points layer back on

    advanced selection … select all points within selected areas

    edit … move to new “SegP1 endpoints” layer

    delete unwanted points on the “SegP1 endpoints” layer( there are
    original SegP1 stations, and the line “endpoints” layer points,
    that were inside the buffers, delete the unwanted line“endpoints”)

    Export to SegP1


    End Procedure

    The step that was missing was the: Crop/Combine – Resample/Split Selected Features at Specified
    Spacing...Sample features at Endpoints Only


    If you don't do this step you get a new point a every vertex of the seismic line when you select: Advanced feature creation … create point features spaced along line... sample features at endpoints only. I'm not sure why this (sample features at endpoints only) doesn't work without the "Crop/Combine" step first? Maybe Global Mapper treats Seismic lines from a SegP1 differently than regular lines.

    At any rate thanks for your help with this. Things are working better now.

    Regards
    Logsmith
Sign In or Register to comment.