[jira] [Created] (GEODE-6830) offheap FreeListManager has synchronization that hurts multi-threaded access

Darrel Schneider created GEODE-6830: --- Summary: offheap FreeListManager has synchronization that hurts multi-threaded access Key: GEODE-6830 URL: https://issues.apache.org/jira/browse/GEODE-6830

[jira] [Updated] (GEODE-6828) DistributedCacheOperation._distribute does synchronization to decide to log trace instead of debug

[ https://issues.apache.org/jira/browse/GEODE-6828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6828: Labels: performance (was: ) > DistributedCacheOperation._distribute does synchronization

[jira] [Created] (GEODE-6828) DistributedCacheOperation._distribute does synchronization to decide to log trace instead of debug

Darrel Schneider created GEODE-6828: --- Summary: DistributedCacheOperation._distribute does synchronization to decide to log trace instead of debug Key: GEODE-6828 URL:

[jira] [Resolved] (GEODE-2685) request that ParitionedRegion getStatistics be a supported operation

[ https://issues.apache.org/jira/browse/GEODE-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-2685. - Resolution: Fixed Fix Version/s: 1.10.0 > request that ParitionedRegion

[jira] [Updated] (GEODE-2685) request that ParitionedRegion getStatistics be a supported operation

[ https://issues.apache.org/jira/browse/GEODE-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-2685: Description: The current implementation of PartitionedRegion getStatistics always throws

[jira] [Resolved] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets

[ https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6472. - Resolution: Fixed > cachePerfStats:gets is double incremented on partitioned region gets

[jira] [Resolved] (GEODE-6794) Returning a client connection to the pool always calls notifyAll

[ https://issues.apache.org/jira/browse/GEODE-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6794. - Resolution: Fixed Fix Version/s: 1.10.0 > Returning a client connection to the

[jira] [Created] (GEODE-6807) changing advisors to cache advice can improve performance

Darrel Schneider created GEODE-6807: --- Summary: changing advisors to cache advice can improve performance Key: GEODE-6807 URL: https://issues.apache.org/jira/browse/GEODE-6807 Project: Geode

[jira] [Updated] (GEODE-6807) changing advisors to cache advice can improve performance

[ https://issues.apache.org/jira/browse/GEODE-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6807: Labels: performance (was: ) > changing advisors to cache advice can improve performance >

[jira] [Created] (GEODE-6794) Returning a client connection to the pool always calls notifyAll

Darrel Schneider created GEODE-6794: --- Summary: Returning a client connection to the pool always calls notifyAll Key: GEODE-6794 URL: https://issues.apache.org/jira/browse/GEODE-6794 Project: Geode

[jira] [Updated] (GEODE-6794) Returning a client connection to the pool always calls notifyAll

[ https://issues.apache.org/jira/browse/GEODE-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6794: Labels: performance (was: ) > Returning a client connection to the pool always calls

[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets

[ https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846184#comment-16846184 ] Darrel Schneider commented on GEODE-6472: - Alberto, instead of doing "if (keyInfo.getBucketId()

[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets

[ https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846170#comment-16846170 ] Darrel Schneider commented on GEODE-6472: - I think pr #3490 is a good change but I don't think we

[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets

[ https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846147#comment-16846147 ] Darrel Schneider commented on GEODE-6472: - It looks like this is the current situation with

[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets

[ https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845368#comment-16845368 ] Darrel Schneider commented on GEODE-6472: - I changed the LocalRegion.get to do nothing on a

[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets

[ https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845354#comment-16845354 ] Darrel Schneider commented on GEODE-6472: - The previous fix for this changed code that is only

[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets

[ https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845068#comment-16845068 ] Darrel Schneider commented on GEODE-6472: - I think the cause of this is that this method:

[jira] [Created] (GEODE-6785) StoppableCountDownLatch reads a system property every time the constructor is called

Darrel Schneider created GEODE-6785: --- Summary: StoppableCountDownLatch reads a system property every time the constructor is called Key: GEODE-6785 URL: https://issues.apache.org/jira/browse/GEODE-6785

[jira] [Updated] (GEODE-6785) StoppableCountDownLatch reads a system property every time the constructor is called

[ https://issues.apache.org/jira/browse/GEODE-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6785: Labels: performance (was: ) > StoppableCountDownLatch reads a system property every time

[jira] [Resolved] (GEODE-6776) ClientSendsStats and ClientStats are broken

[ https://issues.apache.org/jira/browse/GEODE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6776. - Resolution: Fixed Fix Version/s: 1.10.0 > ClientSendsStats and ClientStats are

[jira] [Assigned] (GEODE-6776) ClientSendsStats and ClientStats are broken

[ https://issues.apache.org/jira/browse/GEODE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6776: --- Assignee: Darrel Schneider > ClientSendsStats and ClientStats are broken >

[jira] [Created] (GEODE-6776) ClientSendsStats and ClientStats are broken

Darrel Schneider created GEODE-6776: --- Summary: ClientSendsStats and ClientStats are broken Key: GEODE-6776 URL: https://issues.apache.org/jira/browse/GEODE-6776 Project: Geode Issue Type:

[jira] [Updated] (GEODE-6762) BucketRegion ops do not always need to call createEventForPR

[ https://issues.apache.org/jira/browse/GEODE-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6762: Labels: performance (was: ) > BucketRegion ops do not always need to call

[jira] [Created] (GEODE-6762) BucketRegion ops do not always need to call createEventForPR

Darrel Schneider created GEODE-6762: --- Summary: BucketRegion ops do not always need to call createEventForPR Key: GEODE-6762 URL: https://issues.apache.org/jira/browse/GEODE-6762 Project: Geode

[jira] [Assigned] (GEODE-6761) LocalRegion.initializationThread creates unneeded garbage

[ https://issues.apache.org/jira/browse/GEODE-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6761: --- Assignee: Darrel Schneider > LocalRegion.initializationThread creates unneeded

[jira] [Commented] (GEODE-6761) LocalRegion.initializationThread creates unneeded garbage

[ https://issues.apache.org/jira/browse/GEODE-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836586#comment-16836586 ] Darrel Schneider commented on GEODE-6761: - I have a possible fix in:

[jira] [Created] (GEODE-6761) LocalRegion.initializationThread creates unneeded garbage

Darrel Schneider created GEODE-6761: --- Summary: LocalRegion.initializationThread creates unneeded garbage Key: GEODE-6761 URL: https://issues.apache.org/jira/browse/GEODE-6761 Project: Geode

[jira] [Updated] (GEODE-6761) LocalRegion.initializationThread creates unneeded garbage

[ https://issues.apache.org/jira/browse/GEODE-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6761: Labels: performance (was: ) > LocalRegion.initializationThread creates unneeded garbage >

[jira] [Created] (GEODE-6755) AbstractUpdateOperation.doPutOrCreate calls basicUpdate twice

Darrel Schneider created GEODE-6755: --- Summary: AbstractUpdateOperation.doPutOrCreate calls basicUpdate twice Key: GEODE-6755 URL: https://issues.apache.org/jira/browse/GEODE-6755 Project: Geode

[jira] [Updated] (GEODE-6755) AbstractUpdateOperation.doPutOrCreate calls basicUpdate twice

[ https://issues.apache.org/jira/browse/GEODE-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6755: Labels: performance (was: ) > AbstractUpdateOperation.doPutOrCreate calls basicUpdate

[jira] [Resolved] (GEODE-6686) FilterRoutingInfo.FilterInfo.toData could be optimized to not allocate a byte array every time

[ https://issues.apache.org/jira/browse/GEODE-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6686. - Resolution: Fixed Fix Version/s: 1.10.0 > FilterRoutingInfo.FilterInfo.toData

[jira] [Resolved] (GEODE-6676) org.apache.geode.internal.ByteArrayDataInput.readUTF is not optimal for ASCII strings

[ https://issues.apache.org/jira/browse/GEODE-6676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6676. - Resolution: Fixed Fix Version/s: 1.10.0 >

[jira] [Commented] (GEODE-6663) conserve-sockets=false can cause buffer fragmentation

[ https://issues.apache.org/jira/browse/GEODE-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834071#comment-16834071 ] Darrel Schneider commented on GEODE-6663: - I made a pretty simple change in:

[jira] [Commented] (GEODE-6696) Only create EntryEvenImpl.offHeapLock if off heap is in use.

[ https://issues.apache.org/jira/browse/GEODE-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834041#comment-16834041 ] Darrel Schneider commented on GEODE-6696: - One way to determine if off-heap is being used is to

[jira] [Updated] (GEODE-6696) Only create EntryEvenImpl.offHeapLock if off heap is in use.

[ https://issues.apache.org/jira/browse/GEODE-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6696: Priority: Minor (was: Major) > Only create EntryEvenImpl.offHeapLock if off heap is in

[jira] [Resolved] (GEODE-6670) GemFireCacheImpl.getCacheServers should not allocate a new ArrayList everytime it is called

[ https://issues.apache.org/jira/browse/GEODE-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6670. - Resolution: Fixed Fix Version/s: 1.10.0 > GemFireCacheImpl.getCacheServers should

[jira] [Resolved] (GEODE-6687) org.apache.geode.internal.ByteArrayDataInput can be used in place of ByteArrayInputStream+DataInputStream

[ https://issues.apache.org/jira/browse/GEODE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6687. - Resolution: Fixed > org.apache.geode.internal.ByteArrayDataInput can be used in place of

[jira] [Resolved] (GEODE-6698) Reduce transient String creation in Get70.cmdExecute

[ https://issues.apache.org/jira/browse/GEODE-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6698. - Resolution: Fixed Fix Version/s: 1.10.0 > Reduce transient String creation in

[jira] [Commented] (GEODE-6670) GemFireCacheImpl.getCacheServers should not allocate a new ArrayList everytime it is called

[ https://issues.apache.org/jira/browse/GEODE-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832852#comment-16832852 ] Darrel Schneider commented on GEODE-6670: - Some refactoring was done on getCacheServers, in

[jira] [Reopened] (GEODE-6687) org.apache.geode.internal.ByteArrayDataInput can be used in place of ByteArrayInputStream+DataInputStream

[ https://issues.apache.org/jira/browse/GEODE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reopened GEODE-6687: - The fix had a problem in that if you try to read past the end of a ByteArrayDataInput it

[jira] [Resolved] (GEODE-6690) more client/server messages could take advantage of org.apache.geode.internal.cache.tier.sockets.Message.addStringPart(String, true)

[ https://issues.apache.org/jira/browse/GEODE-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6690. - Resolution: Fixed Fix Version/s: 1.10.0 > more client/server messages could take

[jira] [Assigned] (GEODE-6730) checkSameSenderIdsAvailableOnAllNodes performance could be improved

[ https://issues.apache.org/jira/browse/GEODE-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6730: --- Assignee: Darrel Schneider > checkSameSenderIdsAvailableOnAllNodes performance

[jira] [Created] (GEODE-6730) checkSameSenderIdsAvailableOnAllNodes performance could be improved

Darrel Schneider created GEODE-6730: --- Summary: checkSameSenderIdsAvailableOnAllNodes performance could be improved Key: GEODE-6730 URL: https://issues.apache.org/jira/browse/GEODE-6730 Project:

[jira] [Updated] (GEODE-6730) checkSameSenderIdsAvailableOnAllNodes performance could be improved

[ https://issues.apache.org/jira/browse/GEODE-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6730: Labels: performance (was: ) > checkSameSenderIdsAvailableOnAllNodes performance could be

[jira] [Assigned] (GEODE-6698) Reduce transient String creation in Get70.cmdExecute

[ https://issues.apache.org/jira/browse/GEODE-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6698: --- Assignee: Darrel Schneider > Reduce transient String creation in Get70.cmdExecute >

[jira] [Issue Comment Deleted] (GEODE-6690) more client/server messages could take advantage of org.apache.geode.internal.cache.tier.sockets.Message.addStringPart(String, true)

[ https://issues.apache.org/jira/browse/GEODE-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6690: Comment: was deleted (was: A related, more specific, ticket is:

[jira] [Issue Comment Deleted] (GEODE-6698) Reduce transient String creation in Get70.cmdExecute

[ https://issues.apache.org/jira/browse/GEODE-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6698: Comment: was deleted (was: I think this is one case of the more general:

[jira] [Assigned] (GEODE-6690) more client/server messages could take advantage of org.apache.geode.internal.cache.tier.sockets.Message.addStringPart(String, true)

[ https://issues.apache.org/jira/browse/GEODE-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6690: --- Assignee: Darrel Schneider > more client/server messages could take advantage of >

[jira] [Resolved] (GEODE-6702) InternalDistributedMember equals could be optimized

[ https://issues.apache.org/jira/browse/GEODE-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6702. - Resolution: Fixed Fix Version/s: 1.10.0 > InternalDistributedMember equals could

[jira] [Resolved] (GEODE-6687) org.apache.geode.internal.ByteArrayDataInput can be used in place of ByteArrayInputStream+DataInputStream

[ https://issues.apache.org/jira/browse/GEODE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6687. - Resolution: Fixed Fix Version/s: 1.10.0 >

[jira] [Updated] (GEODE-6657) BridgeServer.MAX_INCOMING_DATA and BridgeServer.MAX_INCOMING_MSGS do not work correctly together

[ https://issues.apache.org/jira/browse/GEODE-6657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6657: Description: If you set both the following system properties: 

[jira] [Resolved] (GEODE-6673) DistributedCacheOperation._distribute has some unneeded HashSet allocations

[ https://issues.apache.org/jira/browse/GEODE-6673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6673. - Resolution: Fixed Fix Version/s: 1.10.0 > DistributedCacheOperation._distribute

[jira] [Resolved] (GEODE-6704) AbstractRegion.allGatewaySenderIds can be improved

[ https://issues.apache.org/jira/browse/GEODE-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6704. - Resolution: Fixed Fix Version/s: 1.10.0 > AbstractRegion.allGatewaySenderIds can

[jira] [Resolved] (GEODE-6688) InternalDistributedMember could use readInt instead of readInteger

[ https://issues.apache.org/jira/browse/GEODE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6688. - Resolution: Fixed Fix Version/s: 1.10.0 > InternalDistributedMember could use

[jira] [Resolved] (GEODE-6674) Put65 has unneeded allocation of StringBuilder

[ https://issues.apache.org/jira/browse/GEODE-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6674. - Resolution: Fixed Fix Version/s: 1.10.0 > Put65 has unneeded allocation of

[jira] [Resolved] (GEODE-6692) DataSerializer.readString can be optimized for zero length strings

[ https://issues.apache.org/jira/browse/GEODE-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-6692. - Resolution: Fixed Fix Version/s: 1.10.0 > DataSerializer.readString can be

[jira] [Assigned] (GEODE-6704) AbstractRegion.allGatewaySenderIds can be improved

[ https://issues.apache.org/jira/browse/GEODE-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6704: --- Assignee: Darrel Schneider > AbstractRegion.allGatewaySenderIds can be improved >

[jira] [Commented] (GEODE-6698) Reduce transient String creation in Get70.cmdExecute

[ https://issues.apache.org/jira/browse/GEODE-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829356#comment-16829356 ] Darrel Schneider commented on GEODE-6698: - I think this is one case of the more general:

[jira] [Commented] (GEODE-6690) more client/server messages could take advantage of org.apache.geode.internal.cache.tier.sockets.Message.addStringPart(String, true)

[ https://issues.apache.org/jira/browse/GEODE-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829358#comment-16829358 ] Darrel Schneider commented on GEODE-6690: - A related, more specific, ticket is:

[jira] [Created] (GEODE-6705) client/server messaging can allocate a large amount of memory when serializing small parts

Darrel Schneider created GEODE-6705: --- Summary: client/server messaging can allocate a large amount of memory when serializing small parts Key: GEODE-6705 URL: https://issues.apache.org/jira/browse/GEODE-6705

[jira] [Updated] (GEODE-6705) client/server messaging can allocate a large amount of memory when serializing small parts

[ https://issues.apache.org/jira/browse/GEODE-6705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6705: Labels: performance (was: ) > client/server messaging can allocate a large amount of

[jira] [Updated] (GEODE-6704) AbstractRegion.allGatewaySenderIds can be improved

[ https://issues.apache.org/jira/browse/GEODE-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6704: Labels: performance (was: ) > AbstractRegion.allGatewaySenderIds can be improved >

[jira] [Created] (GEODE-6704) AbstractRegion.allGatewaySenderIds can be improved

Darrel Schneider created GEODE-6704: --- Summary: AbstractRegion.allGatewaySenderIds can be improved Key: GEODE-6704 URL: https://issues.apache.org/jira/browse/GEODE-6704 Project: Geode Issue

[jira] [Updated] (GEODE-6704) AbstractRegion.allGatewaySenderIds can be improved

[ https://issues.apache.org/jira/browse/GEODE-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6704: Priority: Minor (was: Major) > AbstractRegion.allGatewaySenderIds can be improved >

[jira] [Updated] (GEODE-6703) FilterRoutingInfo.readInternalDistributedMember allocations could be optimized

[ https://issues.apache.org/jira/browse/GEODE-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6703: Labels: performance (was: ) > FilterRoutingInfo.readInternalDistributedMember allocations

[jira] [Created] (GEODE-6703) FilterRoutingInfo.readInternalDistributedMember allocations could be optimized

Darrel Schneider created GEODE-6703: --- Summary: FilterRoutingInfo.readInternalDistributedMember allocations could be optimized Key: GEODE-6703 URL: https://issues.apache.org/jira/browse/GEODE-6703

[jira] [Updated] (GEODE-6702) InternalDistributedMember equals could be optimized

[ https://issues.apache.org/jira/browse/GEODE-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6702: Labels: performance (was: ) > InternalDistributedMember equals could be optimized >

[jira] [Created] (GEODE-6702) InternalDistributedMember equals could be optimized

Darrel Schneider created GEODE-6702: --- Summary: InternalDistributedMember equals could be optimized Key: GEODE-6702 URL: https://issues.apache.org/jira/browse/GEODE-6702 Project: Geode

[jira] [Assigned] (GEODE-6702) InternalDistributedMember equals could be optimized

[ https://issues.apache.org/jira/browse/GEODE-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6702: --- Assignee: Darrel Schneider > InternalDistributedMember equals could be optimized >

[jira] [Assigned] (GEODE-6695) ClientProxyMembershipID.canonicalReference allocates lots of objects

[ https://issues.apache.org/jira/browse/GEODE-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6695: --- Assignee: (was: Darrel Schneider) > ClientProxyMembershipID.canonicalReference

[jira] [Commented] (GEODE-6695) ClientProxyMembershipID.canonicalReference allocates lots of objects

[ https://issues.apache.org/jira/browse/GEODE-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16824410#comment-16824410 ] Darrel Schneider commented on GEODE-6695: - Another problem with the canonicalization of

[jira] [Updated] (GEODE-6331) WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover. testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover fails to connect to VM

[ https://issues.apache.org/jira/browse/GEODE-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6331: Labels: flaky (was: ) >

[jira] [Commented] (GEODE-6695) ClientProxyMembershipID.canonicalReference allocates lots of objects

[ https://issues.apache.org/jira/browse/GEODE-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823608#comment-16823608 ] Darrel Schneider commented on GEODE-6695: - I prototyped a fix for this here: 

[jira] [Assigned] (GEODE-6695) ClientProxyMembershipID.canonicalReference allocates lots of objects

[ https://issues.apache.org/jira/browse/GEODE-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6695: --- Assignee: Darrel Schneider > ClientProxyMembershipID.canonicalReference allocates

[jira] [Created] (GEODE-6695) ClientProxyMembershipID.canonicalReference allocates lots of objects

Darrel Schneider created GEODE-6695: --- Summary: ClientProxyMembershipID.canonicalReference allocates lots of objects Key: GEODE-6695 URL: https://issues.apache.org/jira/browse/GEODE-6695 Project:

[jira] [Commented] (GEODE-6692) DataSerializer.readString can be optimized for zero length strings

[ https://issues.apache.org/jira/browse/GEODE-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823431#comment-16823431 ] Darrel Schneider commented on GEODE-6692: - I have a fix in: 

[jira] [Updated] (GEODE-6692) DataSerializer.readString can be optimized for zero length strings

[ https://issues.apache.org/jira/browse/GEODE-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6692: Labels: performance (was: ) > DataSerializer.readString can be optimized for zero length

[jira] [Created] (GEODE-6692) DataSerializer.readString can be optimized for zero length strings

Darrel Schneider created GEODE-6692: --- Summary: DataSerializer.readString can be optimized for zero length strings Key: GEODE-6692 URL: https://issues.apache.org/jira/browse/GEODE-6692 Project:

[jira] [Assigned] (GEODE-6692) DataSerializer.readString can be optimized for zero length strings

[ https://issues.apache.org/jira/browse/GEODE-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6692: --- Assignee: Darrel Schneider > DataSerializer.readString can be optimized for zero

[jira] [Created] (GEODE-6691) Callers of org.apache.geode.internal.security.SecurityService.authorize(Resource, Operation, String, String) could be optimized by passing the key Object instead of alway

Darrel Schneider created GEODE-6691: --- Summary: Callers of org.apache.geode.internal.security.SecurityService.authorize(Resource, Operation, String, String) could be optimized by passing the key Object instead of always converting it to a

[jira] [Updated] (GEODE-6691) Callers of org.apache.geode.internal.security.SecurityService.authorize(Resource, Operation, String, String) could be optimized by passing the key Object instead of alway

[ https://issues.apache.org/jira/browse/GEODE-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6691: Labels: performance (was: ) > Callers of >

[jira] [Updated] (GEODE-6690) more client/server messages could take advantage of org.apache.geode.internal.cache.tier.sockets.Message.addStringPart(String, true)

[ https://issues.apache.org/jira/browse/GEODE-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6690: Labels: performance (was: ) > more client/server messages could take advantage of >

[jira] [Created] (GEODE-6690) more client/server messages could take advantage of org.apache.geode.internal.cache.tier.sockets.Message.addStringPart(String, true)

Darrel Schneider created GEODE-6690: --- Summary: more client/server messages could take advantage of org.apache.geode.internal.cache.tier.sockets.Message.addStringPart(String, true) Key: GEODE-6690 URL:

[jira] [Updated] (GEODE-6689) adviseSameAsyncEventQueueIds and adviseSameGatewaySenderIds allocate an ArrayList on every call

[ https://issues.apache.org/jira/browse/GEODE-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6689: Labels: performance (was: ) > adviseSameAsyncEventQueueIds and adviseSameGatewaySenderIds

[jira] [Commented] (GEODE-6689) adviseSameAsyncEventQueueIds and adviseSameGatewaySenderIds allocate an ArrayList on every call

[ https://issues.apache.org/jira/browse/GEODE-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823292#comment-16823292 ] Darrel Schneider commented on GEODE-6689: - I have a fix for this in: 

[jira] [Assigned] (GEODE-6689) adviseSameAsyncEventQueueIds and adviseSameGatewaySenderIds allocate an ArrayList on every call

[ https://issues.apache.org/jira/browse/GEODE-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6689: --- Assignee: Darrel Schneider > adviseSameAsyncEventQueueIds and

[jira] [Created] (GEODE-6689) adviseSameAsyncEventQueueIds and adviseSameGatewaySenderIds allocate an ArrayList on every call

Darrel Schneider created GEODE-6689: --- Summary: adviseSameAsyncEventQueueIds and adviseSameGatewaySenderIds allocate an ArrayList on every call Key: GEODE-6689 URL:

[jira] [Commented] (GEODE-6688) InternalDistributedMember could use readInt instead of readInteger

[ https://issues.apache.org/jira/browse/GEODE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823282#comment-16823282 ] Darrel Schneider commented on GEODE-6688: - I have a possible for this in: 

[jira] [Updated] (GEODE-6688) InternalDistributedMember could use readInt instead of readInteger

[ https://issues.apache.org/jira/browse/GEODE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6688: Priority: Minor (was: Major) > InternalDistributedMember could use readInt instead of

[jira] [Updated] (GEODE-6688) InternalDistributedMember could use readInt instead of readInteger

[ https://issues.apache.org/jira/browse/GEODE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6688: Labels: performance (was: ) > InternalDistributedMember could use readInt instead of

[jira] [Assigned] (GEODE-6688) InternalDistributedMember could use readInt instead of readInteger

[ https://issues.apache.org/jira/browse/GEODE-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6688: --- Assignee: Darrel Schneider > InternalDistributedMember could use readInt instead of

[jira] [Created] (GEODE-6688) InternalDistributedMember could use readInt instead of readInteger

Darrel Schneider created GEODE-6688: --- Summary: InternalDistributedMember could use readInt instead of readInteger Key: GEODE-6688 URL: https://issues.apache.org/jira/browse/GEODE-6688 Project:

[jira] [Assigned] (GEODE-6687) org.apache.geode.internal.ByteArrayDataInput can be used in place of ByteArrayInputStream+DataInputStream

[ https://issues.apache.org/jira/browse/GEODE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6687: --- Assignee: Darrel Schneider > org.apache.geode.internal.ByteArrayDataInput can be

[jira] [Commented] (GEODE-6687) org.apache.geode.internal.ByteArrayDataInput can be used in place of ByteArrayInputStream+DataInputStream

[ https://issues.apache.org/jira/browse/GEODE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823275#comment-16823275 ] Darrel Schneider commented on GEODE-6687: - I have a possible fix for this in: 

[jira] [Updated] (GEODE-6687) org.apache.geode.internal.ByteArrayDataInput can be used in place of ByteArrayInputStream+DataInputStream

[ https://issues.apache.org/jira/browse/GEODE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6687: Labels: performance (was: ) > org.apache.geode.internal.ByteArrayDataInput can be used in

[jira] [Created] (GEODE-6687) org.apache.geode.internal.ByteArrayDataInput can be used in place of ByteArrayInputStream+DataInputStream

Darrel Schneider created GEODE-6687: --- Summary: org.apache.geode.internal.ByteArrayDataInput can be used in place of ByteArrayInputStream+DataInputStream Key: GEODE-6687 URL:

[jira] [Commented] (GEODE-6686) FilterRoutingInfo.FilterInfo.toData could be optimized to not allocate a byte array every time

[ https://issues.apache.org/jira/browse/GEODE-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16823271#comment-16823271 ] Darrel Schneider commented on GEODE-6686: - I have a possible fix for this in: 

[jira] [Updated] (GEODE-6686) FilterRoutingInfo.FilterInfo.toData could be optimized to not allocate a byte array every time

[ https://issues.apache.org/jira/browse/GEODE-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-6686: Labels: performance (was: ) > FilterRoutingInfo.FilterInfo.toData could be optimized to

[jira] [Assigned] (GEODE-6686) FilterRoutingInfo.FilterInfo.toData could be optimized to not allocate a byte array every time

[ https://issues.apache.org/jira/browse/GEODE-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-6686: --- Assignee: Darrel Schneider > FilterRoutingInfo.FilterInfo.toData could be optimized

[jira] [Created] (GEODE-6686) FilterRoutingInfo.FilterInfo.toData could be optimized to not allocate a byte array every time

Darrel Schneider created GEODE-6686: --- Summary: FilterRoutingInfo.FilterInfo.toData could be optimized to not allocate a byte array every time Key: GEODE-6686 URL:

<    5   6   7   8   9   10   11   12   13   14   >