Re: Registering process on the fly (performance)

Hi,

uploading new XPDL into shark is expensive operation. However, in shark1.1 it is up to 5 times faster than in shark1.0, depending on
XPDL.

Normal use case would be to have all XPDLs you need imported, and than to create process instances based on their processes. Than,
the creation of the process instance should be very fast, and is measured in milliseconds.

There is no way to "register" package otherwise than using PackageAdministration, nor to create process instance without having
package "registered".

Regards,
Sasa.

----- Original Message -----
From: "Igor" <[email protected]>
To: <[email protected]>
Sent: Monday, June 27, 2005 2:41 PM
Subject: [shark] Registering process on the fly (performance)


> Hi,
> Description: I create small process in runtime (as xpdl file), then
> register it in Shark (PackageAdministration.openPackage()), then execute
> it.
> It works fine, but has poor (for my purpose) performance. Registering
> package (1 process that has 1 activity) takes ~500 ms (2.4 mhz 1gb)
> Can you advice, please, how can Shark may be tuned? Or may be exists
> some way to register package without create.xpdl first - create Process
> in programmatic way?
>
> Thank you,
> Igor Laberov
>
>
>


--------------------------------------------------------------------------------


>
> --
> You receive this message as a subscriber of the [email protected] mailing list.
> To unsubscribe: mailto:[email protected]
> For general help: mailto:[email protected]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>

--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws