This question is in reference to Atlassian Documentation: Migrating to Another Database
Do you have a pseudo limit on what is considered a large data set that makes the .xml backup and restore a non starter?
I have 1 GB in a DB and 17 GB on disk... about 11k pages. and about 10 versions of each.
This is a good summary of what today's AI platforms can do. What I really appreciate about the list is the point of serverless inference, endpoints, and fine tuning, since each one of them takes care of a specific step towards bringing an AI app from experimental stage to production. The option to go either with managed infrastructure or dedicated resources might also facilitate cost/performance/scalability trade-offs.
The most important thing that should be kept in mind is the fact that when selecting a platform, one should pay attention not only to model performance but also to pricing, latency, API availability, data privacy, model license, and compatibility with the current stack. With the development of AI ecosystem, having a list of evaluation criteria will become just as relevant as knowing your models.
I can help here, we've done this a ton. 17gb attachments is right out, do not back up with XML with attachments.
11k pages, 1gb is a medium sized instance from my point of view, however you may run into Out of Memory errors pointing to heap space even at that size. So even if you choose XML without Attachments, you may need to increase the amount of heap in your JVM to do so.
Restoring attachments and the database from backup may be a more desirable workflow to prevent these sort of configuration changes and issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.