[ https://issues.apache.org/jira/browse/ATLAS-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Bikeev updated ATLAS-4555: --------------------------------- Description: h3. Environment: * Cassandra 3.x, 30GB RAM, 4 CPU VM, maximum read latency 30ms * Solr 7.7, 8 GB of RAM, 4 CPU VM * Tested on both 2.1.x and 2.2.x * Attached configuration and some profiling results when doing delete&purge operations via AtlasClientV2 h3. Problems: * Startup time is 1-2 hours - applying default type-models patches * Deletes and purges rate is around 25 entities per minute, so if there is a thousand records to remove it'll take 40 minutes * When you want to edit an entity with big amount of references (like MySQL instance with a lot of databases) you could wait up to 5 minutes or even more before you see the full edit form was: h3. Environment: * Cassandra 3.x, 30GB RAM, 4 CPU VM, maximum read latency 30ms * Solr 7.7, 8 GB of RAM, 4 CPU VM * Tested on both 2.1.x and 2.2.x h3. Problems: * Startup time is 1-2 hours - applying default type-models patches * Deletes and purges rate is around 25 entities per minute, so if there is a thousand records to remove it'll take 40 minutes * When you want to edit an entity with big amount of references (like MySQL instance with a lot of databases) you could wait up to 5 minutes or even more before you see the full edit form > Atlas is very slow with non-embedded (Cassandra) backend > --------------------------------------------------------- > > Key: ATLAS-4555 > URL: https://issues.apache.org/jira/browse/ATLAS-4555 > Project: Atlas > Issue Type: Bug > Components: atlas-core > Affects Versions: 2.1.0, 2.2.0 > Reporter: Albert Bikeev > Priority: Major > Attachments: atlas-application.properties, > delete-purge-profiling1.png, delete-purge-profiling2_nested-bulk.png, > delete-purge-profiling2_nested-purge.png, hotspot-analysis.png > > > h3. Environment: > * Cassandra 3.x, 30GB RAM, 4 CPU VM, maximum read latency 30ms > * Solr 7.7, 8 GB of RAM, 4 CPU VM > * Tested on both 2.1.x and 2.2.x > * Attached configuration and some profiling results when doing delete&purge > operations via AtlasClientV2 > h3. Problems: > * Startup time is 1-2 hours - applying default type-models patches > * Deletes and purges rate is around 25 entities per minute, so if there is a > thousand records to remove it'll take 40 minutes > * When you want to edit an entity with big amount of references (like MySQL > instance with a lot of databases) you could wait up to 5 minutes or even more > before you see the full edit form -- This message was sent by Atlassian Jira (v8.20.1#820001)