[Maria-developers] Query in size
![](https://secure.gravatar.com/avatar/3ed27dca5b85ae4036a8f0ed4ed08855.jpg?s=120&d=mm&r=g)
Hi all, I just when through a revision~maria-captains/mariadb-java-client/trunk : /src/test/java/org/mariadb/jdbc/BigQueryTest.java (revision 516)Big Query activated in this code contains a character array of size 20000000. This is something that can be modified. All big queries possible cannot occupy this space. This is sort of leading to more of wastage of memory. Can anyone help me understand why this size has been selected when the same could be done at a size (50-90)% lesser. Regards Kavneet Kaur
![](https://secure.gravatar.com/avatar/6b1cecb6596aaa9fe497d5bd2bb2f5c1.jpg?s=120&d=mm&r=g)
From: Maria-developers [mailto:maria-developers-bounces+wlad=montyprogram.com@lists.launchpad.net] On Behalf Of Kavneet Kaur Sent: Sonntag, 24. August 2014 06:21 To: maria-developers@lists.launchpad.net Subject: [Maria-developers] Query in size Hi all, I just when through a revision https://code.launchpad.net/~maria-captains/mariadb-java-client/trunk ~maria-captains/mariadb-java-client/trunk : / <http://bazaar.launchpad.net/~maria-captains/mariadb-java-client/trunk/files /516/src> src/ <http://bazaar.launchpad.net/~maria-captains/mariadb-java-client/trunk/files /516/src/test> test/ <http://bazaar.launchpad.net/~maria-captains/mariadb-java-client/trunk/files /516/src/test/java> java/ <http://bazaar.launchpad.net/~maria-captains/mariadb-java-client/trunk/files /516/src/test/java/org> org/ <http://bazaar.launchpad.net/~maria-captains/mariadb-java-client/trunk/files /516/src/test/java/org/mariadb> mariadb/ <http://bazaar.launchpad.net/~maria-captains/mariadb-java-client/trunk/files /516/src/test/java/org/mariadb/jdbc> jdbc/BigQueryTest.java (revision 516) Big Query activated in this code contains a character array of size 20000000. This is something that can be modified. All big queries possible cannot occupy this space. This is sort of leading to more of wastage of memory. The size of the query roughly 20MB for this test, which is bigger than maximum size of a single packet in MySQL protocol (roughly 16MB). This is the single reason - test a query, which must be split into multiple packets when this query is sent to the server. Can anyone help me understand why this size has been selected when the same could be done at a size (50-90)% lesser. Regards Kavneet Kaur
participants (2)
-
Kavneet Kaur
-
Vladislav Vaintroub