[ 
https://issues.apache.org/jira/browse/JENA-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stian Soiland-Reyes updated JENA-898:
-------------------------------------
          Component/s: TDB
          Description: 
    mvn clean install 

on Windows, in particular of jena-tdb and jena-jdbc-driver-tdb requires a lot 
of disk space (> 40 GB) as temporary TDB datasets are created per test due to 
the memory mapped files on Windows not being released (JENA-775, JENA-115)

JENA-897 ensures those files are in target/ when running through Maven, so at 
least they are removed on mvn clean.

It might be possible to release the ByteBuffers that lock the memory regions 
using System.gc() (which might not help anyway) - but this adds significant 
overhead (~ 1s on my machine)  -- perhaps this could be done pr 10 tests in a 
@After if on Windows, as a kind of best-effort clean-up?


          Environment: Windows
    Affects Version/s: Jena 2.13.0
                       Jena 2.12.1
              Summary: Building w/tests on Windows requires a lot of disk space 
 (was: B)

> Building w/tests on Windows requires a lot of disk space
> --------------------------------------------------------
>
>                 Key: JENA-898
>                 URL: https://issues.apache.org/jira/browse/JENA-898
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: TDB
>    Affects Versions: Jena 2.12.1, Jena 2.13.0
>         Environment: Windows
>            Reporter: Stian Soiland-Reyes
>
>     mvn clean install 
> on Windows, in particular of jena-tdb and jena-jdbc-driver-tdb requires a lot 
> of disk space (> 40 GB) as temporary TDB datasets are created per test due to 
> the memory mapped files on Windows not being released (JENA-775, JENA-115)
> JENA-897 ensures those files are in target/ when running through Maven, so at 
> least they are removed on mvn clean.
> It might be possible to release the ByteBuffers that lock the memory regions 
> using System.gc() (which might not help anyway) - but this adds significant 
> overhead (~ 1s on my machine)  -- perhaps this could be done pr 10 tests in a 
> @After if on Windows, as a kind of best-effort clean-up?



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

Reply via email to