June 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2007) Performance improvements for Infinispan servers

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2007: -------------------------------------- Summary: Performance improvements for Infinispan servers Key: ISPN-2007 URL: https://issues.jboss.org/browse/ISPN-2007 Project: Infinispan Issue Type: Enhancement Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.FINAL Future improvements for Memcached/HotRod servers: - Get rid of tuples, they're costly. This would require parameters/header objects to be made mutable. - In Memcached, Get rid of any String construction and deal directly with byte[]. This would require converting adding validation to String-represented numbers, booleans...etc. This is by far biggest hotspot in our implementation. - Get rid of any collection (ListBuffer) for parameter parsing in Memcached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-1235) Per class(es) logging settings in testsuite

by Galder Zamarreño (JIRA)

Per class(es) logging settings in testsuite ------------------------------------------- Key: ISPN-1235 URL: https://issues.jboss.org/browse/ISPN-1235 Project: Infinispan Issue Type: Enhancement Components: Test Suite Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.Final Just brainstorming: It'd be very useful to have a way to run the testsuite with normal logging settings but have the ability to define one or more test classes as having TRACE on x.y.z. This could be useful for those elusive failures that only happen when the testsuite runs! Clearly, it'd need some programmatic magic to enable/disable the logging at runtime, but there's some benefit to all this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-1015) Optimize HotRod client to match Memcached performance

by Dan Berindei (JIRA)

Optimize HotRod client to match Memcached performance ----------------------------------------------------- Key: ISPN-1015 URL: https://issues.jboss.org/browse/ISPN-1015 Project: Infinispan Issue Type: Task Reporter: Dan Berindei Assignee: Dan Berindei Load tests show the HotRod protocol performing worse than the Memcached client. Since the HotRod protocol should be easier to parse and we also have the extra topology information, this is quite surprising. We have analyzed the servers and seem to perform about the same, so we need to optimize the client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

6
20
0 / 0

[JBoss JIRA] Created: (ISPN-303) Follow up Jopr demo ideas

by Galder Zamarreno (JIRA)

Follow up Jopr demo ideas ------------------------- Key: ISPN-303 URL: https://jira.jboss.org/jira/browse/ISPN-303 Project: Infinispan Issue Type: Task Components: JMX, reporting and management Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Ideas for a follow up Jopr demo: - Show ISPN-302 in action. - Heiko: About the monitoring schedules : in Administration->System Configuration->Templates you can also "predefine" this, so it gets applied to every new instance (and if wanted also to all existing instances). - Heiko: mention that 30 seconds is too too short for production -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
5
0 / 0

[JBoss JIRA] (ISPN-1959) Reduce size of distribution bundle

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1959: ------------------------------------- Summary: Reduce size of distribution bundle Key: ISPN-1959 URL: https://issues.jboss.org/browse/ISPN-1959 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1 It's currently over 100MB in size, we should be able to reduce it significantly just taking out duplicates. Maybe a better compression -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

5
10
0 / 0

[JBoss JIRA] (ISPN-2122) Overwrite/Implement the missing default File methods

by Thomas Fromm (JIRA)

11 years, 9 months

3
3
0 / 0

[JBoss JIRA] (ISPN-2136) cache.lock(...) with FAIL_SILENTLY flag within OPTIMISTIC tx should fail immediate

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2136: ---------------------------------- Summary: cache.lock(...) with FAIL_SILENTLY flag within OPTIMISTIC tx should fail immediate Key: ISPN-2136 URL: https://issues.jboss.org/browse/ISPN-2136 Project: Infinispan Issue Type: Enhancement Affects Versions: 5.1.5.FINAL Reporter: Thomas Fromm Assignee: Manik Surtani Priority: Minor The error: Caused by: org.infinispan.CacheException: Explicit locking is not allowed with optimistic caches! at org.infinispan.interceptors.locking.OptimisticLockingInterceptor.visitLockControlCommand(OptimisticLockingInterceptor.java:202) ... is currently supressed by FAIL_SILENTLY flag. But this is an usage error not an locking failure, so it should fail immediate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
5
0 / 0

[JBoss JIRA] (ISPN-2132) CLONE - Getting java.lang.StackOverflowError in org.infinispan.transaction.xa.TransactionXaAdapter.toString(TransactionXaAdapter.java:215)

by Paul Jackson (JIRA)

11 years, 9 months

5
11
0 / 0

[JBoss JIRA] (ISPN-2134) Convert TreeCache tests to new cache config API

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-2134: ----------------------------------- Summary: Convert TreeCache tests to new cache config API Key: ISPN-2134 URL: https://issues.jboss.org/browse/ISPN-2134 Project: Infinispan Issue Type: Task Components: Tree API Affects Versions: 5.2.0.ALPHA1 Reporter: Adrian Nistor Assignee: Adrian Nistor Need to replace all usages of the deprecated config API in tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
6
0 / 0

[JBoss JIRA] (ISPN-2101) Eviction does not work with Apache Derby cache loader-- SQL error

by dex chen (JIRA)

dex chen created ISPN-2101: ------------------------------ Summary: Eviction does not work with Apache Derby cache loader-- SQL error Key: ISPN-2101 URL: https://issues.jboss.org/browse/ISPN-2101 Project: Infinispan Issue Type: Bug Components: Core API, Eviction Affects Versions: 5.1.4.FINAL Environment: Infinispan 5.1.4 final, Apache Derby JDBC cache loader configured using Eviction Reporter: dex chen Assignee: Manik Surtani The cache will not be created because of the following sql error: Running sql 'SELECT DATA_COLUMN, ID_COLUMN FROM ISPN_STRING_TABLE_keychain LIMIT ? ERROR org.infinispan.loaders.jdbc.DataManipulationHelper[253] - ISPN008007: SQL error while fetching all StoredEntries java.sql.SQLSyntaxErrorException: Syntax error: Encountered "?" at line 1, column 69. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement40.<init>(Unknown Source) at org.apache.derby.jdbc.Driver40.newEmbedPreparedStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) The problem is that Apache Derby does not support select LIMIT. See here from Derby doc: 5.2. Does Derby support a LIMIT command? ^ Derby does not support the LIMIT syntax. However, Derby 10.4 added the ROW_NUMBER function and Derby 10.7 added the OFFSET and FETCH clauses. Derby also supports limiting the number of rows returned by a query through JDBC. For example, to fetch the first 5 rows of a large table: Statement stmt = con.createStatement(); stmt.setMaxRows(5); ResultSet rs = stmt.executeQuery("SELECT * FROM myLargeTable"); Some related tuning tips are available in this external article. Starting with the 10.4.1.3 release Derby also supports limiting the number of rows using the ROW_NUMBER function. For example, to fetch the first 5 rows of a large table: SELECT * FROM ( SELECT ROW_NUMBER() OVER() AS rownum, myLargeTable.* FROM myLargeTable ) AS tmp WHERE rownum <= 5; The ROW_NUMBER function can also be used to select a limited number of rows starting with an offset, for example: SELECT * FROM ( SELECT ROW_NUMBER() OVER() AS rownum, myLargeTable.* FROM myLargeTable ) AS tmp WHERE rownum > 200000 AND rownum <= 200005; For more information, refer to the ROW_NUMBER built-in function in the Derby Reference Manual (available from the Documentation page). Development notes are available on the OLAPRowNumber wiki page. The LIMIT keyword is not defined in the SQL standard, and is currently not supported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

5
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2012