Increased filesizes

Flyboy · Oct 14th 2012

We are moving our current archive pacs server to new hardware.
When transferring the files between our 2 servers I noticed they are increasing in size, approx 200%.
Both servers are set up with exactly the same configuration.

JPEG2000 support
NKI compressed
Saved as V2

IncomingCompression = n4

When speccing out the new server, we calculated in future growth, but no increase in moving the files.

Is there anyone that can shed any light on why this might be happening and if this is preventable?

Thanks

marcelvanherk · Oct 15th 2012

Hi,

I suspect NKI compression in not working. Which version are you using? And can you post your dicom.ini?

Marcel

marcelvanherk · Oct 15th 2012

Hi,

Sorry, this is a bug introduced in 1.4.16k. Try 1.4.16j instead:

ftp://ftp-rt.nki.nl/outbox/mar…r/ConquestUpdate1416j.zip

Marcel

Flyboy · Oct 16th 2012

Dicom config can be found at the bottom.
Going back to 1.4.16j is not an option. We had severe crashing issues with that version. Sometimes up to 5 times a day in each of our locations.
This was fixed when upgrading to 1.4.16k

I have no real attachment to the NKI format. This is just the format the systems were using when we took over the IT infrastructure.
I started reading more about this in the last couple days and decided that a change to DCM files with jpg lossless compression will do as good a job if not better of saving space, with the added benefit of being compatible with more devices.
I know about the speed difference, which shouldn't be an issue once the initial conversion is completed.

When I was moving the 9TB of nki images to the new server, it was going to finish in 53 hours.
It seems that moving the same amount to DCM and jpg compression will be over 200 hours.

After reading this thread and testing myself I had a couple more questions:
- If there is a bug in the NKI format since the latest version, does that mean all images created since then are larger than supposed to and will need to be recompressed later on to gain space?
- Are there any other considerations in choosing between V2/NKI and DCM/jpg except for compression speed and compatibility?

If one or the other is clearly better I have the ability to switch some servers and storage around to convert all of them to the same format. (for now, that none of the locations has more than 10TB yet)

Code

# This file contains configuration information for the DICOM server
# Do not edit unless you know what you are doing


[sscscp]
MicroPACS                = sscscp
Edition                  = Personal


# Network configuration: server name and TCP/IP port#
MyACRNema                = OSCONQUEST2
TCPPort                  = 115


# Reference to other files: known dicom servers; database layout; sops
ACRNemaMap               = acrnema.map
kFactorFile              = dicom.sql
SOPClassList             = dgatesop.lst


# Host(ignored), name, username and password for ODBC data source
SQLHost                  = localhost
SQLServer                = conquestpacs_s3
Username                 = conquest1
Password                 = ********
BrowseThroughDBF         = 1
DoubleBackSlashToDB      = 0
UseEscapeStringConstants = 0


# Configure database
TruncateFieldNames       = 10
MaxFieldLength           = 254
MaxFileNameLength        = 255
FixPhilips               = 0
FixKodak                 = 0
KeepAlive                = 0
LargeFileSizeKB          = 4096
PrintSquareLandscape     = 0
UseKpacsDecompression    = 1
ZipTime                  = 05:
UIDPrefix                = 1.2.826.0.1.3680043.2.135.734788.53261698
EnableReadAheadThread    = 1
PatientQuerySortOrder    = 
StudyQuerySortOrder      = 
SeriesQuerySortOrder     = 
ImageQuerySortOrder      = 
EnableComputedFields     = 1
IndexDBF                 = 1
PackDBF                  = 0
LongQueryDBF             = 1000
TCPIPTimeOut             = 300
FailHoldOff              = 60
RetryDelay               = 100
RetryForwardFailed       = 0
ImportExportDragAndDrop  = 0
QueueSize                = 128
WorkListMode             = 0
WorkListReturnsISO_IR_100 = 1
DebugLevel               = 4
Prefetcher               = 0
LRUSort                  = 
AllowTruncate            = 
DecompressNon16BitsJpeg  = 1
UseBuiltInJPEG           = 1
LossyQuality             = 95
IgnoreOutOfMemoryErrors  = 0
NoDICOMCheck             = 0
PadAEWithZeros           = 0
FileNameSyntax           = 4


# Configuration of compression for incoming images and archival
DroppedFileCompression   = j2
IncomingCompression      = j2
ArchiveCompression       = as


# Names of the database tables
PatientTableName         = DICOMPatients
StudyTableName           = DICOMStudies
SeriesTableName          = DICOMSeries
ImageTableName           = DICOMImages
DMarkTableName           = DICOMAccessUpdates
RegisteredMOPDeviceTable = RegisteredMOPIDs
UIDToMOPIDTable          = UIDToMOPID
UIDToCDRIDTable          = UIDToCDRID


# Banner and host for debug information
PACSName                 = OSCONQUEST2
OperatorConsole          = 127.0.0.1


# Configure email of error messages
MailHost                 = 
MailPort                 = smtp
MailSignon               = 
MailFromName             = 
MailRcptName1            = 
MailCollectTime          = 1
MailWaitTime             = 10


# Configuration of disk(s) to store images
MAGDeviceThreshhold      = 0
MAGDeviceFullThreshHold  = 30
IgnoreMAGDeviceThreshold = 0
MAGDevices               = 1
MAGDevice0               = F:\pacsimages\
NightlyCleanThreshhold   = 0

Display More

marcelvanherk · Oct 16th 2012

Hi,

I see I need to bring out an update to fix this. I was attempting a full release but that is a lot of work due to the documentation. I will try to do it tonight.

Marcel

Flyboy · Oct 16th 2012

So all images created since 16k are larger than they should be in nki compression?

marcelvanherk · Oct 16th 2012

Yes,

I will bring out an update tonight....

Marcel

marcelvanherk · Oct 16th 2012

Hi,

the update is in the full release 1.4.17alpha on the forum.

Marcel

Flyboy · Oct 16th 2012

Thanks!

Increased filesizes

Participate now!

Share