Hi Petr,
If your TSM server is well sized, I'm afraid, you can't get this kind of
request be faster.
The GUI is slow and needs to completely query ALL the files of a tree-level
before displaying it
For really-big nodes, prefer the CLI.
Is your TSM server heavily loaded when you retrieve your files ?,
what is the cache hit %, if under 99%, increase BUFPOOLSIZE
unless you pick this extra memory from the NT swap file.
when you start a client session for retrieving files, have a look
on your TSM server to the stats for your client node
adsm > q node f=d
will give you some hints about node workload for last session.
rv
> -----Message d'origine-----
> De : Petr Prerost [mailto:[EMAIL PROTECTED]]
> Envoy� : jeudi 15 mars 2001 10:28
> A : [EMAIL PROTECTED]
> Objet : Problems with retrieve in TSM v.4
>
>
> Hello ,
> after upgrade TSM server to 4.1.2 ( NT ) there appear big performance
> problems with retrieve .
> TSM server is small ( DB is 2.5 GB ) but one of client
> archives monthly NTFS
> directory containing
> about 200 000 files. When I tried to retrieve group of files with GUI
> client - expand of each level
> of directory structure take up to 15 minutes - I checked Q
> sess on server
> and session status
> is RUN but no data goes between client and server ( this status don't
> change ) . On the server
> side I checked Q db f=d and I can see large number of buffer
> requests ( more
> than 4 millions ) and
> cache hit ratio slowly decreasing ( I am using 200 MB db
> cache ) . Well
> after 15 minutes GUI show me
> first level of archive files space and when I tried to expand
> next level the
> same story repeat .
>
> Any idea ?
>
>
> Petr P�erost
> H.T.D., spol. s r.o.
> Praha , Pod pr�sekem 12
> �esk� republika/Czech republic
> e-mail [EMAIL PROTECTED]
>
