Server requires some tweaking??

[kenadams]

Hi There,

After upgrading several servers to Pervasive 8.6 from 2000i SP3 we have noticed a drop in btrieve performance from client PCs running the Pervasive client, WIN98. It is a DOS app accessing a database on the Netware servers, so we use btrbox95 and bdosstub. Before the upgrade to 8.6 performance was very good.

NW6.5 SP1, Nss volumes. All Netware settings are at the default level.

Bti.cfg - we have set a cachesize of 100 meg and layer2 cache we have lowered to %10, nwmkde was taking too much RAM at the default layer 2 size of %60.


Are there any tweaks that can be made to the server that might speed things up??

Thanks

 

[marvhuffaker]

You might have better luck putting the database on a Traditional volume. Both Pervasive and Novell will tell you otherwise, but I've done enough testing to say that there is a significant performance hit when putting btreive apps on NSS volumes.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[kenadams]

Yeah I did read a TID that said a tradition volume would be better when we did the original upgrade from 4.11 to 6.5, but the performance on Pervasive 2000i and NSS was pretty good, not as good as a traditional volume but still quick enough to use as a trade off. The performance hit only occured after putting 8.6 on.
My only problem with re-creating the volume as traditional volumes is that its 200+ servers that need doing.

 

[marvhuffaker]

Ah. So you were already on NSS before you upgraded pervasive. I missed that part.

When you upgraded, did it reset your BTI.CFG to defaults? Have you compared old and new BTI.CFG files? Maybe something significant changed there.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[kenadams]

The Pervasive install does reset the bti.cfg but we then adjusted it back to our preferred settings and restarted the server so the settings would take effect.
I'll check it again in case I missed something obvious, maybe 8.6 added something that I don't want.

 

[kenadams]

I can't see much wrong with my bti.cfg, here it is, if anyone has any ideas
[InstallInfo]
InstallDir=Z:\PVSW\
SystemDir=Z:\SYSTEM\
InstallIniName=PTKSETUP.INI
VersionLevel=8.60
PatchLevel=0
BuildLevel=192

[MicroKernel]
MaxFiles=2000
CacheSize=90480

MaxCursors=2000
BalancedTrees=NO
ForceFileVersion=0800
SystemData=YES
MaxDatabases=100
Logging=NO
CompressedBufferSize=5
ExtendedBufferSize=16
MergeSortBufferSize=0
MaxRecSize=16
CachePartitioning=NO
TransDurability=YES
TransLogBufferSize=1024 *
TransLogFileSize=1024 *
SysTransBundleLimit=1000 *
SysTransTimeLimit=10000 *
MaxClients=50
BackgroundThreads=4
WaitLockTimeout=30
TransLogDirectory=SYS:SYSTEM/MKDE/LOG
Trace=NO
TraceFile=SYS:/SYSTEM\MKDE.TRA
TraceDataBufferLength=32
TraceKeyBufferLength=32
TraceOpsList=ALL
LoadRouter=NO
RouterCommBufferSize=16
Use FileIO Mutex=YES
Validate Request=NO
MaxCacheUsage=5
TransLogging=YES
Max Pending IO=1024
File Growth Factor=15
Page Server Allow Client Cache=YES
Prompt For Client Credentials=NO
Allow Client-Stored Credentials=YES
[Database Names]
DBNamesDirectory=SYS:/SYSTEM
[Btrieve Interface]
Embedded Spaces=NO
[Btrieve Communications Manager]
MaxWorkerThreads=16
MaxRecSize=65116
MaxClients=100
MaxReceivePacketSize=1500
Use SAP=AUTODETECT
Supported Protocols=SPX,TCPIP
Listen IP Address=
TCP/IP Multihomed=YES
Enable AutoReconnect=NO
AutoReconnect Timeout=180


These settings are as they were on Pervasive 2000 apart from the parts I marked with an *, the top 2 of these are higher than 2000i and the bottom 2 are new to Pervasive 8.6.

 

[bytehd]

im not a btrieve guru, but i would check some of those
parameters that caught my eye.

BackgroundThreads=4

any parameters that are like 4, 8, 16, 32
perhaps 1000, 5000 are better?

You can also use Monitor.NLM to watch the kernel times
when running the client app...to see which NLM is
working harder than it should.

George Walkey
Senior Geek in charge

http://www.insyncva.com