Hexagon Geospatial
MENU

Support ECW / JP2

The ECW (Enhanced Compressed Wavelet) and JP2 formats are standard compressing processes in many Hexagon Geospatial products. This discussion board focuses on the production and use of the ECW/JP2.
Showing results for 
Search instead for 
Do you mean 
Reply
Regular Contributor
Posts: 226
Registered: ‎10-12-2015

WARNING: Setting the thread count to 4, which exceeds the CPU core count of 2, is not recommended

I'm running GeoCompressor on a system that reports two CPUs, one core per CPU.

PS C:\Windows\system32> Get-WmiObject -class Win32_processor | ft systemname,Name,DeviceID,NumberOfCores,NumberOfLogical
Processors, Addresswidth

systemname Name DeviceID NumberOfCores NumberOfLogicalProc Addresswidth
essors
---------- ---- -------- ------------- ------------------- ------------
CCOGISSDITE01 Intel(R) Xeon(R)... CPU0 1 1 64
CCOGISSDITE01 Intel(R) Xeon(R)... CPU1 1 1 64


PS C:\Windows\system32>

 

In the XML Project file I don't specify the THREADS parameter - I leave it to GeoCompressor to work it out.

Extract:

<imagecompressor version="1.1">
<compresstask operation="create" method="tile" tempdir="D:\temp\ApolloBasemapGeneration" logfile="H:\Imagery\BasemapsThematic\stagingMosaic\CCCBaseMapStreet\batch\mosaicS0000000133-295598949812-ecw-57317c19-9634-4b89-99d5-5b187b4be2f3.log" loglevel="info" memcache="0.4" interactive="false">
<inputs>

 

In the log file I see:

Computer name: ccogissdite01
Platform: Platform Unknown
CPU Model: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz
CPU Spec: 2 Cores, 2 Threads, 2 Processors, NUMA disabled (2 total)
Memory: 32.00 GB
Temp dir: D:\temp\ApolloBasemapGeneration

2018-02-06 07:58:28:519 [264] INFO ImageCompressor::Main - WARNING: Setting the thread count to 4, which exceeds the CPU core count of 2, is not recommended

2018-02-06 08:05:47:209 [264] INFO ImageCompressor::Main - Validating input: ... (436 seconds)

 

Deployed: geocompressor-v16.0-ep02-win-x64 (16.00.0000.00199)

 

I'm thinking I need to update my scripts to specifically detect and populate the number of threads in the project file rather than leave it to GeoCompressor to detect?

 

 

Staff
Posts: 139
Registered: ‎02-05-2016

Re: WARNING: Setting the thread count to 4, which exceeds the CPU core count of 2, is not recommende

Hi Shaun,

Looks like you are still using the old Geocompressor 2016.2 (build # 199). Please try the latest  version (build # 236) available at the following  location:

 

https://download.hexagongeospatial.com/downloads/ecw/geocompressor-2016-patch-02-windows

 

 

Regards

Partha Roy

Regular Contributor
Posts: 226
Registered: ‎10-12-2015

Re: WARNING: Setting the thread count to 4, which exceeds the CPU core count of 2, is not recommende

ooops, I typed the wrong version number in. GeoCompressor 16.0.2.236 is deployed, not 199.

Staff
Posts: 139
Registered: ‎02-05-2016

Re: WARNING: Setting the thread count to 4, which exceeds the CPU core count of 2, is not recommende

[ Edited ]

Hi Shaun,

It looks like the application is failing due to some incompatibility issues of the input data. Please create a support request and send your data. We will investigate your problem there.

 

Regards

Partha Roy

Regular Contributor
Posts: 226
Registered: ‎10-12-2015

Re: WARNING: Setting the thread count to 4, which exceeds the CPU core count of 2, is not recommende

Hi Partha,

 

The ECW actually seems to generate fine. My concern is around too many threads affecting performance as indicated in the Geocompressor user guide.

I've logged ticket 00024548

 

thanks

Shaun

Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Service Request through our Support Portal.