Menu
▾
▴
Forums
- Performance, db configuration 3
- GT.MUntersttzung+Diskussion 20
- Bindings, other languages 3
- Developers 60
- Tools, GUI 5
- Applications, Cache migration 9
- Features, sockets 18
- Help 175
- Open Discussion 65
- Applications, ESI Objects 23
- Applications, DTM migration 8
- Applications, web access, CGI 13
- Applications, VistA 8
- Features, file I/O, named pipe 7
- Performance, Help! 2
- Performance, system config 9
- Applications, KB_SQL 2
- Clients, PHP 2
- Performance, design for 3
- Applications, web servers 2
- Applications, web access, misc 3
- Features, 1995, misc 3
- Applications, DSM migration 1
- Applications, suitability for 1
speed GT.M
1.
what are the best settings in ^GDE (or other routine)
in block size(=1024 or 4096 ?) or allotment, or in any other parameteres
so GT.M will be most robust ?
2. what parameteres can be changed in already defined .dat ?
and what parameters has to be make before defining the .dat ?
rgrds
EL
1. GT.M robustness is not affected by the block size. However, block size affects performance. Factors to consider:
a. larger block sizes are more IO efficient; smaller block sizes are more CPU efficient.
b. the most IO efficient block sizes are a multiple of the natural block size of the file system.
Ultimately, you should choose block size based on considerations of performance, record size and maximum database size.
2. Block size is immutable once a database is created. Read the mupip and dse documentation: it will tell you what can be changed. For anything that they don't tell you how to change, assume that it cannot be easily and safely changed.
Regards
-- Bhaskar