The XCC/.NET implementation embeds XCC/Java within
it. The advantage of this is that both versions of XCC
run the same code. The drawback is that there is a
relatively large Java library that must be initialized
at startup. Depending on the environment, this can
result in a short startup delay as the CLR loads the
libraries.
The spinup penalty is only incurred once. For a
long-running software stack, such as a web application,
this is not significant. If you launch a new process
for each query, then you will incur that startup penalty
each time.
On Feb 18, 2009, at 2:06 AM, Soumadri_Roy wrote:
Hi,
I have used XDBC .Net client API earlier and was comparing XCC .Net
client API, in terms of “Turnaround time”. It has been observed that
XDBC API returned the results approx. 500ms faster than XCC APIs.
I have executed a cts:search with cts:element:word:query.
My query is pulling around 18500 elements from the database.
Although XDBC is now deprecated, is there any way to improve the
result fetching time using XCC.
Thanks and Regards
Soumadri Roy
Mobile: 09986832356
<image001.gif>
DISCLAIMER:
This email (including any attachments) is intended for the sole use
of the intended recipient/s and may contain material that is
CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance
by others or copying or distribution or forwarding of any or all of
the contents in this message is STRICTLY PROHIBITED. If you are not
the intended recipient, please contact the sender by email and
delete all copies; your cooperation in this regard is appreciated.
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
---
Ron Hitchens {[email protected]} 650-655-2351
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
