Re: [infinispan-dev] Cache Store Does'nt Work Async Whenever Modification is Inside Transaction

Created https://jira.jboss.org/jira/browse/ISPN-340 You can vote. On Tue, Jan 26, 2010 at 3:21 PM, Sanne Grinovero <sanne.grinovero(a)gmail.com&gt; wrote: > +1 > I don't know if it's correct to consider it a bug, but choices on JIRA > are limited. > I would really need this - performance impact is high - and hope they > could fix it before 4.0 > > Regards, > Sanne > > 2010/1/26 Amin Abbaspour&lt;a.abbaspour(a)gmail.com&gt;: >> Yes Philippe, I think it is a bug. >> >> This totally ruins all attempts to create a write-behind async store. >> I don't know if JBoss Cache had the same issue or not, but for many >> use-cases (including ours) one will need both TX and write-behind >> simultaneously. >> >> OK, I will open a bug in Jira for 4.0.0-GA. >> >> Amin >> >> On Tue, Jan 26, 2010 at 2:12 PM, Philippe Van Dyck&lt;pvdyck(a)gmail.com&gt; wrote: >>> Sounds like a good idea. >>> How do you qualify it ? Bug ? (perf) Improvement ? >>> It has a major impact on performance when using the S3 CacheStore, so I >>> would like it to be a "performance bug". >>> WDYT ... especially regarding the planning of the next release ? >>> Phil >>> On Tue, Jan 26, 2010 at 11:28 AM, Amin Abbaspour&lt;a.abbaspour(a)gmail.com&gt; >>> wrote: >>>> >>>> Hi, >>>> >>>> Should I open a jira task for this? >>>> >>>> Amin >>>> >>>> On Sat, Jan 23, 2010 at 4:59 PM, Amin Abbaspour&lt;a.abbaspour(a)gmail.com&gt; >>>> wrote: >>>>> I guess this is a somehow a bug or typo. >>>>> >>>>> Transactions and stores are two separate concepts. While it sounds to >>>>> flush to normal store at the TX commit but when one knowingly sets >>>>> store as async, he accepts the risk of consistence in favor of speed. >>>>> >>>>> I expect this to be fixed (or at least discussed) before GA. >>>>> >>>>> Amin >>>>> >>>>> On Sat, Jan 23, 2010 at 3:48 PM, Philippe Van Dyck&lt;pvdyck(a)gmail.com&gt; >>>>> wrote: >>>>>> I do confirm this behavior. >>>>>> Transactions and asynchronous updates may seem antagonistic, but they >>>>>> are >>>>>> not on a multi-level cache. >>>>>> I plan to use a synchronous transactional disk cache and a second non >>>>>> transactional asynchronous s3 cache, to get the best of both worlds. >>>>>> Since the asynchronous aspect of the s3 cache will not allow me to get >>>>>> any >>>>>> feedback (aka Future), I want it to 'write-behind' in the background >>>>>> (and >>>>>> hope everything goes well). >>>>>> I will wait for the qi4j v1 release (probably Monday), adapt infinispan >>>>>> to >>>>>> the blobstore of jClouds and take a closer look at this in a couple of >>>>>> weeks. >>>>>> Phil >>>>>> >>>>>> On Sat, Jan 23, 2010 at 12:58 PM, Amin Abbaspour >>>>>> <a.abbaspour(a)gmail.com&gt; >>>>>> wrote: >>>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> Regarding >>>>>>> http://community.jboss.org/wiki/Write-ThroughAndWrite-BehindCaching >>>>>>> , Even if Syncer is in Async mode, but if we modify a key inside a >>>>>>> transaction boundary it is always stored synchronously! Why is it so? >>>>>>> How can I have both locking and async store. FYI I use JBossTM >>>>>>> Standalone. >>>>>>> >>>>>>> Regards, >>>>>>> Amin Abbaspour >>>>>>> _______________________________________________ >>>>>>> infinispan-dev mailing list >>>>>>> infinispan-dev(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> infinispan-dev mailing list >>>>>> infinispan-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>>>>> >>>>> >>>> _______________________________________________ >>>> infinispan-dev mailing list >>>> infinispan-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>> >>> >>> _______________________________________________ >>> infinispan-dev mailing list >>> infinispan-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/infinispan-dev >>> >> >> _______________________________________________ >> infinispan-dev mailing list >> infinispan-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/infinispan-dev > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev