Discussion Locked

Multi volume on single Hard Disk

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are going to install a Novell Netware 4.11 Server. We have two MS-DOS (Clipper/DBF) software applications to use. Now if we create two volumes in single hard disk of server and copy each one application on each volume. Can we get better speed & performance than single volume ?

11 replies

by jimbb

No, doesn't make any difference. The important thing is to have the cache-tuning optimised, and that you do for the entire server, not per volume or partition. There are a few documents on Novell's knowledgebase describing the different parameters, and how to let them interact. The only thing you should know is if you have big or small reads or writes, and which of both (read or write) is the most important.

Jim

by don christner

No, because all data still is going through a single channel of the hard disk controller. You would need two independant controllers in order to get greater speed.

Don

by curacao_dejavu

nope,
You need raid 5 with striped parity to do that, so the OS will write on the 2 (or more) partitions at the same time.

Leopold

by estebandelatorre

No It will be better to setup a single volume (other that the sys: one allways) to set both applications there.
The main reason is that all resources and cache size will be better distributed among the request. There's no need of setup two FAT's, two transaction logs, two of everything.
If you need better speed, just add ram, as much as memory the server have, the better results.
If not clear: The sys: volume should be only for the OS, not to share with data. A new volume (not two as you mention) should be defined (as small as possible) in order to hold both applications.

by s_pryce

It shouldn't matter! However, Clipper being a DOS app conforms to DOS 3.1 file and record locking standard, with some extras depending who wrote the app which was then compiled with which ver of clipper.
The problems your very likely to have are;
1. Clipper lacks of a write lock, it locks the first byte of the file its going to write and a "mystical" byte, 1 billion on in the file.(under dos 3.1 this can't exist, netware it can) and uses this 2nd lock to signify a write lock. Makes a mess of the file system, particulary with block sub allocation turned on.
Put each clipper app in its own volume with 16K or 32K block size (you got big records 32, small 16). Volume size at twice the size of the largest you think the database will get.
2. File & record locks, multi-user access will create file and record locks like its going out of fashion. Your need to set the following parms.
Maximum Record Locks Per Connection
Maximum File Locks Per Connection
Maximum Record Locks
Maximum File Locks
I've seen a good w/s try to create 3000 locks a second. Experiment!
3. Be prepared for file corruption, it comes from caching in the workstation and is hard to avoid unless you cripple the workstation. Its probably easier to get the client to run a bootable dos only system to use clipper.
In all - have fun, Your database is 15 yrs old, treat it to a re-write!
How it helps
Spryce

This discussion is closed to new replies.