Summary
This article explains why 360Eyes jobs may run slower than usual, particularly during the snapshot copy step, and how to resolve the most common cause of this issue.
Symptoms
You may notice one or more of the following:
- 360Eyes jobs are taking significantly longer to complete than they used to.
- The slowdown is most noticeable during the snapshot copy stage of the job.
- Performance was previously normal and has gradually degraded over time.
- The issue is not tied to a specific job or schedule, but seems to affect jobs broadly.
Cause
The snapshot copy step is one of the most database-intensive parts of a 360Eyes job, since it requires reading and writing large volumes of data in a short window. Because of this, it's often the first place where database performance issues become noticeable, even when the issue actually affects the database more broadly.
In most cases, this slowdown is caused by index fragmentation in the underlying database. Databases use indexes to quickly locate data, similar to how an index in a book helps you find information without reading every page. Over time, as records are added, changed, and removed, these indexes can become fragmented, meaning the data they reference is no longer stored in a clean, organized order. A fragmented index still works, but it takes more effort for the database to use, which slows down data-intensive operations like snapshot copy.
Resolution
The recommended fix is to defragment the indexes in the database used by 360Eyes. This process reorganizes the index data so the database can retrieve information efficiently again, restoring normal performance.
The exact steps to defragment indexes depend on which database platform your organization uses (such as SQL Server, PostgreSQL, or Oracle), as each has its own tools and procedures for this type of maintenance. Because of this, we recommend the following approach:
- Identify which database platform is running for 360Eyes.
- Consult your database administrator, IT team, or your database vendor's official documentation for the recommended way to check and defragment indexes on that platform.
- Perform the defragmentation during a maintenance window, as this process can temporarily use additional system resources.
- After defragmentation completes, re-run a 360Eyes job to confirm that snapshot copy performance has improved.
If you don't have a database administrator on staff or aren't sure how to proceed, your database vendor's support team can typically assist with this maintenance.
Preventing Recurrence
Index fragmentation naturally builds up again over time as the database continues to be used. To avoid recurring slowdowns, we recommend scheduling regular index maintenance (for example, monthly or quarterly, depending on database activity) as part of your routine database upkeep.
Still Need Help?
If you've defragmented your database indexes and are still experiencing slow snapshot copy times, please contact us so we can help investigate further.