• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • 😌 This community is user driven. Be polite with other users.
    • 👉 Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • 💸 Purchase a Pro Subscription to get access to active software support and faster ticket response times.

Migrated from MyISAM to InnoDB to host DB on Amazon RDS. Now much slower?

Status
Not open for further replies.
K

Kai

Chevereto Member
Hi. I couldn't find a thread about this. My explore pages have a time to first byte of 8s (then with InnoDB optimization and super expensive instance 5s).

From what I can gather it has to do with this query:

SQL: 
SELECT *, chv_images.image_id FROM chv_images LEFT JOIN chv_storages ON chv_images.image_storage_id = chv_storages.storage_id LEFT JOIN chv_users ON chv_images.image_user_id = chv_users.user_id LEFT JOIN chv_albums ON chv_images.image_album_id = chv_albums.album_id LEFT JOIN chv_categories ON chv_images.image_category_id = chv_categories.category_id LEFT JOIN chv_meta ON chv_images.image_id = chv_meta.image_id WHERE chv_images.image_nsfw = 0 AND (chv_albums.album_privacy NOT IN ('private','private_but_link','custom') OR chv_albums.album_privacy IS NULL OR chv_albums.album_user_id IS NULL) ORDER BY chv_images.image_id DESC LIMIT 0,15;

On top of InnoDB seeming to be the issue, I think the SELECT * is also grabbing new columns I've added for other uses, which Chevereto doesn't use at all on explore pages.

I am using 3.7.1 (I cannot easily upgrade for reasons) with MySQL 5.7. I've messed with all the MySQL settings for too long pulling hair out.

I did find the Chevereto class but I don't know what to change or if that's even what I should be doing. Any help appreciated but I know you are busy.

Thanks Rodolfo
 
Is there a preferred or recommended relational db that plays nice with AWS auto scaling? (and Chevereto)
 
The solution here is that you should definitely update your Chevereto.
 
With the level of customization applied, that is not possible without a week or two of work to resolve something that should be less difficult.

I'm contemplating bringing the new db back into the old db @ localhost. It'll cost more and won't scale, but one expensive instance I need to manually scale would at least give me some room to breathe and work on the proposed update.
 
Find a way to do it because you are missing tons of mysql improvements and several security patches.
 
Status
Not open for further replies.
Back
Top