GA version of APM that was causing big amount of topological changes to be stored. As a result, the database size was growing very quickly and was making complexity of query evaluation hard.
One should take a look on size of tables to decide if cleanup procedure will be needed.
Release : 10.7.0
Component : Introscope
Resolution: These problems are fixed in hotfixes, so please install latest available
Workaround: Utilize APM Database Optimization by cleanup
Manual steps for cleanup database:
Cleanup decision:
select external_id, history from (
select vertex_id, count(1) as history from appmap_vertices
where start_time > (CURRENT_DATE - INTERVAL '5 day')
group by vertex_id
order by 2 desc
limit 20) t
join appmap_id_mappings m on t.vertex_id=m.vertex_id
Oracle:
select external_id, history from (
select vertex_id, count(1) as history from appmap_vertices
where start_time > (sysdate - 5)
group by vertex_id
order by 2 desc) t
join appmap_id_mappings m on t.vertex_id=m.vertex_id
where rownum < 20
Optimize tables in Oracle:
alter table appmap_edges enable row movement;
alter table appmap_vertices enable row movement;
alter table appmap_attribs enable row movement;
alter table appmap_edges shrink space compact;
alter table appmap_vertices shrink space compact;
alter table appmap_attribs shrink space compact;