Hello Siby,
I think we should keep this conversation based on Geode if possible. I
think GemFire has their own support channels that you might be able to
contact for help specific to GemFire...
As for the commit conflicts, I assume you are using transactions? Also, I
am not aware of a specific M
Jason,
We are using the Map feature of GemFire and update throws CommitComflict
exceptions when the same key is updated from multiple places at the same
time, how can this be resolved ? This happens only at high contention
though. We are retrying , but still even after a couple of retries it does
thank you that clarifieded my queries.
--
Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
Pdx and indexing are different altogether. Pdx affects the serialization
of the object. Indexing affects querying speed. Together, they should
improve the entire query speed because querying can cause
deserializations. With Pdx it should speed up look ups by not causing full
deserialization per
is there an advantage of using one vs other
index on a field vs PDX serialization as both are used in query execution.
--
Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
Jason,
how can we use both together, isnt it redundant as both serve the same
purpose ? making retrieval faster ?
--
Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
The index and pdx serialization are orthogonal. You will be able to use
both together
On Tue, Oct 2, 2018 at 10:50 AM siby_sekar wrote:
> Thank you Jason that was really helpful.
>
> Can we use index and PDXSerialization together on a field. Here in this
> case
> we will be searching by session
Thank you Jason that was really helpful.
Can we use index and PDXSerialization together on a field. Here in this case
we will be searching by sessionId,
but should we assign just PDxSerialization or index or can we use both on
sessionId ?
thanks,
Siby.
--
Sent from: http://apache-geode-incuba
I think if you embed the sessionId into your value object and create an
index, that should perform better. I am assuming if you embed the sesionId
that you would then be doing queries more similar to sessionId = X or
sessionId like sessionId%. Being able to use the index will prevent the
query en
for us sessionId is not the actual key field.
It will be something like some arbitrarystring+sessionid
and we will be running queries with - like "%sessionId%" to find all
entries having a particular sessionid.
In this case to improve performance can we apply any index ?
is this approach bet
as part of the value field and then apply PDX
serialization on the value objects and run queries and can have = comparison
on value objects. Would this be faster than running queries on key fields.
If we can run queries on key fields itself what is the real advantage of
having PDX serialization
Usually key fields are faster
--
Mike Stolz
Principal Engineer, GemFire Product Lead
Mobile: +1-631-835-4771
On Fri, Sep 28, 2018 at 2:49 PM siby_sekar wrote:
> Which is more performant running queries on key fields or non key fields?
>
> we have an object in the form
>
> sess
Which is more performant running queries on key fields or non key fields?
we have an object in the form
sessionid : { Listmessages}
and message can be like {
id1,
sessionid,
name
}
etc.
--
Sent from: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/
13 matches
Mail list logo
