Reply to thread

Message

<blockquote data-quote="ElementalCrisis" data-source="post: 1245963" data-attributes="member: 159827">With Version 3.6, which was released almost two years ago, Max added internal caching which greatly improved speeds which made using SQLite a viable option for large collections. Since then we've made additional changes to the internal caching system with the sole purpose of eventually deprecating MySQL and SQL Server as it becomes more of a hassle to provide support for three different types of DB's. Initial loading when starting Shoko Server is not as fast as say MySQL or SQL Server but even then its at max an extra 10 seconds or so. Of course if Shoko needs to do any regen work then that will also delay the initial startup but that's true with all three DB types. However even this should be improved with the changes currently being made as part of the .NET Standard conversion as we're dropping nHibernate and using EF instead. MA3 users probably won't see any drastic changes until we switch it over to the new API we're working on. If you want an idea on what to expect, compare MA3 against Nakamori, our Kodi plugin as that uses APIv2 which is the base for the new API we're working on. However it should be noted that da3dsoul has fine-tuned Nakamori which is something MA3 currently lacks.</blockquote>

[QUOTE="ElementalCrisis, post: 1245963, member: 159827"] With Version 3.6, which was released almost two years ago, Max added internal caching which greatly improved speeds which made using SQLite a viable option for large collections. Since then we've made additional changes to the internal caching system with the sole purpose of eventually deprecating MySQL and SQL Server as it becomes more of a hassle to provide support for three different types of DB's. Initial loading when starting Shoko Server is not as fast as say MySQL or SQL Server but even then its at max an extra 10 seconds or so. Of course if Shoko needs to do any regen work then that will also delay the initial startup but that's true with all three DB types. However even this should be improved with the changes currently being made as part of the .NET Standard conversion as we're dropping nHibernate and using EF instead. MA3 users probably won't see any drastic changes until we switch it over to the new API we're working on. If you want an idea on what to expect, compare MA3 against Nakamori, our Kodi plugin as that uses APIv2 which is the base for the new API we're working on. However it should be noted that da3dsoul has fine-tuned Nakamori which is something MA3 currently lacks. [/QUOTE]

Verification