You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Yuri Simione (Jira)" <ji...@apache.org> on 2022/04/05 07:30:00 UTC

[jira] [Created] (SLING-11251) Apache Sling Post Servlet consumes too much resources during content ingestion

Yuri Simione created SLING-11251:
------------------------------------

             Summary: Apache Sling Post Servlet consumes too much resources during content ingestion
                 Key: SLING-11251
                 URL: https://issues.apache.org/jira/browse/SLING-11251
             Project: Sling
          Issue Type: Bug
          Components: Servlets
    Affects Versions: Starter 12
         Environment: Mac OS, OpenJDK 1.8, Intel I9, 16gb RAM.
            Reporter: Yuri Simione
         Attachments: image-2022-04-05-09-09-08-725.png, image-2022-04-05-09-19-55-925.png

I am testing performances of Apache Sling 12, configured with Oak Segment Store, started with the -Xmx4g parameter. I'm using a multi-threaded Python script (I tried with 30 threads down to 5 concurrent threads). The tool loads thousands of contents on new oak:Unstructured nodes using the standard {*}Sling Post servlet{*}. Before to start the import I stopper the Lucene bundle. Initially performances are good (about 200 new documents/sec). Soon, after the tool has ingested about 20k new nodes, the speed drops to a few nodes per second. I analyzed the JVM and noticed that the memory allocated for some threads grows by several GBs without ever going down (see attached images). If I stop the import tool, the situation does not change. The only way to solve this problem is to turn off the Sling instance and restart it. Is it normal for threads to acquire resources that are never released?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)