Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Size of ir.translation table over total db size

Archives

Contributors

auditlog incompatible with partner_firstname

How to lookup psc team for repo?

Size of ir.translation table over total db size

Hi all, 

we've recently found out that on a "clean" db (not yet in production), with around 350 modules installed and no customer data imported, the ir.translation table occupies about 95% of the space - about 9GB. Just two languages are enabled.

On another db in production since 2+ years, out of 7,5 GB of the db size, ir.translations occupies 21% of the space (1,6GB). Just one language is enabled here.

We were a bit surprised to find out about the table size and we're looking for feedback on whether these proportions sound "regular" to you. 

Thanks!

--

Francesco Foresti
Sicurpharma Srl
by Francesco Foresti - 07:11 - 24 Jan 2023

Follow-Ups

  • Re: Size of ir.translation table over total db size
    Thank you all for your valuable responses, I'll let you know what we find out. 

    Cheers!

    Il giorno mer 25 gen 2023 alle ore 08:07 Martin Trigaux (Odoo) <notifications@odoo-community.org> ha scritto:
    On 24/01/2023 19:11, Francesco Foresti wrote:

    we've recently found out that on a "clean" db (not yet in production), with around 350 modules installed and no customer data imported, the ir.translation table occupies about 95% of the space - about 9GB. Just two languages are enabled.

    On another db in production since 2+ years, out of 7,5 GB of the db size, ir.translations occupies 21% of the space (1,6GB). Just one language is enabled here.

    Your clean db stats seems to the roof. On the Github PR odoo/odoo#45958 I measured the size with 7 languages installed on a new database. I did not have 350 modules installed but the size was measured in MB, not GB.
    I suspect one (or more) of the module is polluting the table. Check the entries based on the module field to find the culprit.

    On a production database, it may grow a lot but 1.6 Gb still seems excessive (I don't think we reached that size on odoo.com).
    On old database, orphan translations (pointing to records that no longer exists) may increase the size of the table unnecessarily but 2 years is not that old either.
    I would start by investigating what takes so much space in this table.

    Best,

    Martin

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe



    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790

    by Francesco Foresti - 09:50 - 25 Jan 2023
  • Re: Size of ir.translation table over total db size
    On 24/01/2023 19:11, Francesco Foresti wrote:

    we've recently found out that on a "clean" db (not yet in production), with around 350 modules installed and no customer data imported, the ir.translation table occupies about 95% of the space - about 9GB. Just two languages are enabled.

    On another db in production since 2+ years, out of 7,5 GB of the db size, ir.translations occupies 21% of the space (1,6GB). Just one language is enabled here.

    Your clean db stats seems to the roof. On the Github PR odoo/odoo#45958 I measured the size with 7 languages installed on a new database. I did not have 350 modules installed but the size was measured in MB, not GB.
    I suspect one (or more) of the module is polluting the table. Check the entries based on the module field to find the culprit.

    On a production database, it may grow a lot but 1.6 Gb still seems excessive (I don't think we reached that size on odoo.com).
    On old database, orphan translations (pointing to records that no longer exists) may increase the size of the table unnecessarily but 2 years is not that old either.
    I would start by investigating what takes so much space in this table.

    Best,

    Martin
    by Martin Trigaux - 08:06 - 25 Jan 2023
  • Re: Size of ir.translation table over total db size

    Good idea but vacuum full only in off peak times and after a proper backup (for the own safety) ;-)

    Best Frederik

    Am 24.01.23 um 20:51 schrieb Moises Lopez:
    Hi,

    There is an issue related with vacuum claim space in tables


    Also, you didn't mention the PG version used

    But try running a "vacuum full"


    On Tue 24 Jan 2023 at 12:11 p.m. Francesco Foresti <notifications@odoo-community.org> wrote:
    Hi all, 

    we've recently found out that on a "clean" db (not yet in production), with around 350 modules installed and no customer data imported, the ir.translation table occupies about 95% of the space - about 9GB. Just two languages are enabled.

    On another db in production since 2+ years, out of 7,5 GB of the db size, ir.translations occupies 21% of the space (1,6GB). Just one language is enabled here.

    We were a bit surprised to find out about the table size and we're looking for feedback on whether these proportions sound "regular" to you. 

    Thanks!

    --

    Francesco Foresti
    Sicurpharma Srl

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    --
    Moisés López Calderón
    Mobile: (+521) 477-752-22-30
    Twitter: @moylop260
    hangout: moylop260@vauxoo.com
    http://www.vauxoo.com - Odoo Gold Partner
    Twitter: @vauxoo

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    -- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Phone:  +49 4181 13503-12
Fax:    +49 4181 13503-10
Mobil:  +49 179 3901819

Email: frederik.kramer@initos.com
Web:   www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
    by Frederik Kramer - 09:06 - 24 Jan 2023
  • Re: Size of ir.translation table over total db size
    Hi,

    There is an issue related with vacuum claim space in tables


    Also, you didn't mention the PG version used

    But try running a "vacuum full"


    On Tue 24 Jan 2023 at 12:11 p.m. Francesco Foresti <notifications@odoo-community.org> wrote:
    Hi all, 

    we've recently found out that on a "clean" db (not yet in production), with around 350 modules installed and no customer data imported, the ir.translation table occupies about 95% of the space - about 9GB. Just two languages are enabled.

    On another db in production since 2+ years, out of 7,5 GB of the db size, ir.translations occupies 21% of the space (1,6GB). Just one language is enabled here.

    We were a bit surprised to find out about the table size and we're looking for feedback on whether these proportions sound "regular" to you. 

    Thanks!

    --

    Francesco Foresti
    Sicurpharma Srl

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    --
    Moisés López Calderón
    Mobile: (+521) 477-752-22-30
    Twitter: @moylop260
    hangout: moylop260@vauxoo.com
    http://www.vauxoo.com - Odoo Gold Partner
    Twitter: @vauxoo
    by Moisés López Calderón - 08:50 - 24 Jan 2023
  • Re: Size of ir.translation table over total db size
    Maybe such a size is because there's a lot of translatable content in such DB (like big product descriptions including e-commerce and a lot of products).

    Regards.
    by Pedro M. Baeza - 08:31 - 24 Jan 2023