msuters
Active Member
Hi all,
Our Terminal Server environments (the W environments, eg WPD7334) show
poorer performance than our "fat client" environments (eg PD7334). For
example, there is a noticeable difference in the time it takes to do a
Find on the Address book (P01012), on the Voucher Entry (P0411) and
other screens. The difference seems to happen in a wide variety of
applications. The performance difference is very noticeable, and a great
negative influence on the perception of JDE in our organisation.
In the W environments, most business functions are mapped to run on the
application server, rather than running locally on the client. The
performance hit may come from the overhead of the client communicating
with the application server to run the business functions, or from the
code on the server running more slowly than on the client. (It is not
the performance of the server itself. A fat client installed on the
server runs as well as any other fat client, but the W environment still
runs more slowly.)
JDE have been looking at this problem for over a week now, but have not
suggested any option for improving the performance of the W environment,
apart from using OCM to map the business functions to run locally. But
then we might as well not use the W environments at all.
Firstly, have other people seen this difference in performance between W
environments and fat clients? If so, what can we do to resolve the
problem?
Secondly, is there a danger mapping the business functions to run
locally in the W environments? I have heard that if the citrix server
becomes overloaded, business functions can fail during operations,
causing data integrity issues. Have people seen this, is it a danger, or
is it just hearsay?
Thanks,
Mark Suters
ERP8, U1, SP22_F1, Win2000, SQL2000, Citrix XP FR3
------------------------------------------------------------------------
---
Mark Suters - Senior Network and Applications Engineer
Stockland Group
P: 02 9561 2671 F: 02 9020 8323 M: 0417 318 245
E: [email protected]
------------------------------------------------------------------------
---
#####################################################################################
Note:
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are not
the intended recipient. Stockland and any of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks.
Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorized to state them to be the
views of any such entity.
Thank You.
#####################################################################################
Our Terminal Server environments (the W environments, eg WPD7334) show
poorer performance than our "fat client" environments (eg PD7334). For
example, there is a noticeable difference in the time it takes to do a
Find on the Address book (P01012), on the Voucher Entry (P0411) and
other screens. The difference seems to happen in a wide variety of
applications. The performance difference is very noticeable, and a great
negative influence on the perception of JDE in our organisation.
In the W environments, most business functions are mapped to run on the
application server, rather than running locally on the client. The
performance hit may come from the overhead of the client communicating
with the application server to run the business functions, or from the
code on the server running more slowly than on the client. (It is not
the performance of the server itself. A fat client installed on the
server runs as well as any other fat client, but the W environment still
runs more slowly.)
JDE have been looking at this problem for over a week now, but have not
suggested any option for improving the performance of the W environment,
apart from using OCM to map the business functions to run locally. But
then we might as well not use the W environments at all.
Firstly, have other people seen this difference in performance between W
environments and fat clients? If so, what can we do to resolve the
problem?
Secondly, is there a danger mapping the business functions to run
locally in the W environments? I have heard that if the citrix server
becomes overloaded, business functions can fail during operations,
causing data integrity issues. Have people seen this, is it a danger, or
is it just hearsay?
Thanks,
Mark Suters
ERP8, U1, SP22_F1, Win2000, SQL2000, Citrix XP FR3
------------------------------------------------------------------------
---
Mark Suters - Senior Network and Applications Engineer
Stockland Group
P: 02 9561 2671 F: 02 9020 8323 M: 0417 318 245
E: [email protected]
------------------------------------------------------------------------
---
#####################################################################################
Note:
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are not
the intended recipient. Stockland and any of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks.
Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorized to state them to be the
views of any such entity.
Thank You.
#####################################################################################
