inline

On Fri, Aug 7, 2009 at 5:38 PM, Jason Meckley <[email protected]>wrote:

>
> My windows service seems to constantly increase is memory consumption
> (task manager>processes>memory usage). My first thought is this has to
> do with Saga State.
>
> Currently I'm using the InMemorySagaStatePersister. I thought this
> might be the issue, maybe in memory is for testing, not production
> (like NH has a HashTable cache for testing). Is this correct?
>

Pretty much, it has no support for concurrency control (that is, it will
work, but last write wins).
That said, make sure to Complete your sagas, because this is how the IMSP
will know to remove them.


> If the memory consumption is due to the InMemorySagaStatePersister I
> have a choice between DistributedHashTableSagaSatePersister and
> OptimisticDistributedHashTableSagaSatePersister. What is the
> difference?
>

How you handle concurrency control between them.

http://ayende.com/Blog/archive/2009/08/08/rhino-service-bus-dht-saga-sate-persisters-options.aspx

>
> Implementing either DHT or ODHT would require my state objects to
> Implement IVersionedState. This is simple enough with auto properties.
> I don't have the set the versioning properties, RSB handles that,
> correct?
>

Yes.


> I then need to register mergers for my State objects. Again that is
> simple enough; implementing ISagaStateMerger<>. When I create the
> resulting state I don't need to worry about the versioned properties,
> correct? just set the properties that contain business value and
> return. RSB will handle version properites.


You can take a look at the samples in the tests.
In general, I would say you want the optimistic one.


>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to