Tim

I have been using a RemoteProcedure server using DLL to connect to DBSRVR
(customized application) and it is going so good. This works exactly I
expect. The server is listening connections on port 12007 and when it
receives a new call it starts a new thread to process the remote procedure.
So far, so good.

There is only one DBSRVR project with two server components DBISAM and my
server. If I deploy my server into a new application what should be the
impact of performance. It is already a multi-thread application.

Thanks for any comments.

Eduardo

Eduardo,

<< There is only one DBSRVR project with two server components DBISAM and my
server. If I deploy my server into a new application what should be the
impact of performance. It is already a multi-thread application. >>

There shouldn't be any difference at all provided that you keep the threads
running at tpLower thread priority like they are in the DBISAM Database
Server.   That will ensure that the application's tpNormal threads always
get priority and never suffer due to load from the other server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

> There shouldn't be any difference at all provided that you keep the
> threads running at tpLower thread priority like they are in the DBISAM
> Database Server.   That will ensure that the application's tpNormal
> threads always get priority and never suffer due to load from the other
> server.

This is what I suspect.
BTW, where the standard dbsrvr defines thread priority ?
I think the default is "normal".

Eduardo

Eduardo,

<< BTW, where the standard dbsrvr defines thread priority ? I think the
default is "normal". >>

It always uses tpLower thread priority for its threads.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

I have found it in dbisamen.pas and dbisamsv.pas

Thanks

Eduardo