You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2015/11/04 00:55:27 UTC

[jira] [Commented] (JAMES-1634) Slow Cassandra tests

    [ https://issues.apache.org/jira/browse/JAMES-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988509#comment-14988509 ] 

Tellier Benoit commented on JAMES-1634:
---------------------------------------

Hi the team :-)

With the solution you propose you habe a speed up of ~5. That's good but still slow ( ~ 10 min tests for all Cassandra tests).

My suggestion (maybe quite crazy, but maybe you'll like it !) 

 - us a ramdisk for cassandra-unit storage. This test does this : http://www.planetcassandra.org/blog/reduce-integration-test-time-by-94-by-using-ramdisk/

Ok, but creating a ram disk is complicated. Mount command can be used inside docker using –privileged option. 

So the idea is to mount the RAM disk in docker and expose an ENV variable.
If the ENV variable is present, we use the yaml to configure cassandra-unit to use the RAM disk. If not we launch it normaly.

Don't know if this is easily doable and if you'll have the time to do this, but this is worth mentionning ;-)

> Slow Cassandra tests
> --------------------
>
>                 Key: JAMES-1634
>                 URL: https://issues.apache.org/jira/browse/JAMES-1634
>             Project: James Server
>          Issue Type: Bug
>            Reporter: Antoine Duprat
>
> Cassandra tests are slow, tables creation takes approximatively 25 seconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org