db2 is currently on CVZ and db3 is currently on SVZS.
Most wikis are on db2 however this is now become an extremely big burden on performance, new wikis, logins and just general work. @Reception123 has been "interrogating" me on how we can (in theory) kill db2 in its current state and on evaluation it is in theory something we can do and is something we seriously SHOULD do.
I can evaluate and move suitable databases to db3 to lighten the load on a new db2 however realistically we need db2's current disk space to be <70G otherwise we're walking back into no space trap.
@labster needs to just acknowledge the plan. He has a budget at hand for this so quick estimates for him will be:
- best case: -$9/mo ($30 -> $21) (adequate space)
- worst case: +$12/mo ($30 -> 2*$21) (not enough space, more than 2 new 3G servers = 200G extra space)
- best-worst case: -$2/mo ($30 -> $28) (not enough space, temporary space solution with a 4G server)
Depending on the above, if we go with the best case, ManageWiki becomes an urgent priority as we need dynamic server allocation for new wikis. If we go with best-worse case, it becomes a high priority as we need dynamic server allocation. If we go with worst case, ManageWiki is still necessary but we can use a database list to allocate wikis in separate cluster and can avoid manual definitions. @Southparkfan
I am going to start on evaluating and move things off db2 as fit to allow a better assessment of the situation for now.