/ doc / DocFrag / ARCCore.StreamProcessorP.IndividualStorageFileSize / Attribute

Attribute

Edit keys at this level only

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Description = Max size (in bytes) for a single storage file before a new file is created by call to -StreamProcessor.CreateNewStorageFile-.0x000D0x000ANote: The actual resulting file-size will vary depending on actual method used for measuring file-size.0x000D0x000A0x000D0x000AThe value to be chosen will affect in the following manner:0x000D0x000A0x000D0x000A1) Memory usage for -CoreDB- / -ArmDB- (smaller value is better). These nodes do not need to hold the whole database in memory, but they will as a minimum have to read the last (the current) storage file into memory, and possible also some older files for subscribing clients which do not yet have an updated copy of the data relevant for their -Subscription-.0x000D0x000A(note that memory used will under normal circumstances be more than double the size of the storage file.)0x000D0x000A0x000D0x000A2) Response time at startup (smaller value is better). For instance for -CoreDB-, if all clients are 'up-to-date', then having a small current storage file is advantageous because only that (last) file have to be read into memory at startup.0x000D0x000A0x000D0x000A3) -DataRetention- (smaller value is better). Smaller filesize would mean each file gets processed quicker, meaning it should affect less the performance of more critical processing (data retention is assumed not time-critical / performance critical).0x000D0x000A0x000D0x000A4) If a file-system (file copy) method of backup is used, then more copying will be needed the greater the file size chosen (smaller value is better).0x000D0x000ANOTE: You can as well do backup through an -Subscription-, instead of by file-copying at the -CoreDB- server.0x000D0x000A5) Debugging / administrative tasks. Opening of a storage file in an editor (smaller value is maybe better). Changing content of storage values (higher value is maybe better, a lesser number of files to contend with).0x000D0x000A0x000D0x000A6) The actual number of files stored in the -LocalStorageFolder- (higher value is better). All filenames are read by -StartTCPIPCommunication- at startup so having a huge amount of files may be less optimal.0x000D0x000A0x000D0x000A7) Coordination among different -CoreDB- instances (smaller value is better). (currently not implemented, Apr 2020). It is assumed much easier to coordinate with smaller filesizes. Like calculating hash-values in order to ensure identical files for instance, which in turn will ensure that -ClientUpdatePosition- between different -CoreDB- instances are compatible.0x000D0x000A
LongDescription = Note that setting a really huge value could breach limits of object storage in RAM (like number of items in a List0x003C0x003E (because index is 32 bit only) and similar).0x000D0x000AA value of up to 1GB is considered quite safe though.0x000D0x000A" +TODO: Research further these limitations
PKTypeAttribute/BoilerplateCodeProperties = // Autogenerated boilerplate code. Paste into your class as needed.0x000D0x000Apublic Int64 IndividualStorageFileSize0x007B0x000D0x000A  get =0x003E IP.GetPV0x003CInt640x003E(StreamProcessorP.IndividualStorageFileSize)0x003B0x000D0x000A  set =0x003E IP.SetPV(StreamProcessorP.IndividualStorageFileSize, value)0x003B0x000D0x000A0x007D0x000D0x000Apublic AddIndividualStorageFileSize(Int64 individualStorageFileSize) =0x003E IP.AddPV(StreamProcessorP.IndividualStorageFileSize, individualStorageFileSize)0x003B0x000D0x000A/// 0x003Csee cref="PKTypeAttributeP.IsObligatory"/0x003E for StreamProcessorP.IndividualStorageFileSize, therefore Get as possible null, Get with default value and TryGet not offered here0x000D0x000A0x000D0x000A0x000D0x000A
PKTypeAttribute/Cardinality = HistoryOnly
PKTypeAttribute/DefaultValue = 100000000
PKTypeAttribute/Description = Max size (in bytes) for a single storage file before a new file is created by call to -StreamProcessor.CreateNewStorageFile-.0x000D0x000ANote: The actual resulting file-size will vary depending on actual method used for measuring file-size.0x000D0x000A0x000D0x000AThe value to be chosen will affect in the following manner:0x000D0x000A0x000D0x000A1) Memory usage for -CoreDB- / -ArmDB- (smaller value is better). These nodes do not need to hold the whole database in memory, but they will as a minimum have to read the last (the current) storage file into memory, and possible also some older files for subscribing clients which do not yet have an updated copy of the data relevant for their -Subscription-.0x000D0x000A(note that memory used will under normal circumstances be more than double the size of the storage file.)0x000D0x000A0x000D0x000A2) Response time at startup (smaller value is better). For instance for -CoreDB-, if all clients are 'up-to-date', then having a small current storage file is advantageous because only that (last) file have to be read into memory at startup.0x000D0x000A0x000D0x000A3) -DataRetention- (smaller value is better). Smaller filesize would mean each file gets processed quicker, meaning it should affect less the performance of more critical processing (data retention is assumed not time-critical / performance critical).0x000D0x000A0x000D0x000A4) If a file-system (file copy) method of backup is used, then more copying will be needed the greater the file size chosen (smaller value is better).0x000D0x000ANOTE: You can as well do backup through an -Subscription-, instead of by file-copying at the -CoreDB- server.0x000D0x000A5) Debugging / administrative tasks. Opening of a storage file in an editor (smaller value is maybe better). Changing content of storage values (higher value is maybe better, a lesser number of files to contend with).0x000D0x000A0x000D0x000A6) The actual number of files stored in the -LocalStorageFolder- (higher value is better). All filenames are read by -StartTCPIPCommunication- at startup so having a huge amount of files may be less optimal.0x000D0x000A0x000D0x000A7) Coordination among different -CoreDB- instances (smaller value is better). (currently not implemented, Apr 2020). It is assumed much easier to coordinate with smaller filesizes. Like calculating hash-values in order to ensure identical files for instance, which in turn will ensure that -ClientUpdatePosition- between different -CoreDB- instances are compatible.0x000D0x000A
PKTypeAttribute/EnumMember = IndividualStorageFileSize
PKTypeAttribute/EnumType = StreamProcessorP
PKTypeAttribute/IsObligatory = True
PKTypeAttribute/LongDescription = Note that setting a really huge value could breach limits of object storage in RAM (like number of items in a List0x003C0x003E (because index is 32 bit only) and similar).0x000D0x000AA value of up to 1GB is considered quite safe though.0x000D0x000A" +TODO: Research further these limitations
PKTypeAttribute/Type = Int64

Edit single sub keys only: Description / LongDescription / PKTypeAttribute

Generated 2025-08-03 09:33:57.651 UTC