Skip to Content

Contributors

  • Re: Performance of /shop controller
    If you use profiler module,

    Port this and measure only /shop request

    https://github.com/OCA/server-tools/pull/1986

    Or use this directly with workers=0 in controlled environment:

    https://github.com/OCA/server-tools/pull/1369

    Then you can know which python function calls the sql_db and which ORM call was it, and know more about what generates the offending SQL.

    And of course follow Moises advice in order to actually get the offending SQL



    Apr 11, 2021 09:31:56 Lorenzo Battistini <elbaddy@gmail.com>:

    Hi all,

    in our odoo 12 deployments we usually detect a time to first byte above 1.5 sec for /shop pages.

    We already cache \/web\/(static|image|content)\/ in nginx and installed website_js_below_the_fold, but odoo server is the bottleneck at the moment.

    I profiled these requests with py-spy and noticed that execute function (odoo/sql_db.py) takes most of the time.

    Did anybody analyze these queries and have experience or modules to share?

    Thanks!

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


    by Tom Blauwendraat - 10:50 - 11 Apr 2021
  • Re: Performance of /shop controller
    It could be a lot of things

    I was realized that computing prices is heavy.
    But prefetching tables too as
     - website.user_id.partner_id.lang
    Missing indexes and so on.

    There are fixes using LRU cache in newer versions but if you have detected that queries are slow you can try getting the postgresql log in order to analyze it


    On Sun 11 Apr 2021 at 2:31 a.m. Lorenzo Battistini <elbaddy@gmail.com> wrote:
    Hi all,

    in our odoo 12 deployments we usually detect a time to first byte above 1.5 sec for /shop pages.

    We already cache \/web\/(static|image|content)\/ in nginx and installed website_js_below_the_fold, but odoo server is the bottleneck at the moment.

    I profiled these requests with py-spy and noticed that execute function (odoo/sql_db.py) takes most of the time.

    Did anybody analyze these queries and have experience or modules to share?

    Thanks!

    _______________________________________________
    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 - 09:41 - 11 Apr 2021
  • Performance of /shop controller
    Hi all,

    in our odoo 12 deployments we usually detect a time to first byte above 1.5 sec for /shop pages.

    We already cache \/web\/(static|image|content)\/ in nginx and installed website_js_below_the_fold, but odoo server is the bottleneck at the moment.

    I profiled these requests with py-spy and noticed that execute function (odoo/sql_db.py) takes most of the time.

    Did anybody analyze these queries and have experience or modules to share?

    Thanks!


    by Lorenzo Battistini. - 09:30 - 11 Apr 2021
  • Re: OCA and security notices
    Hi Pedro,
    
    It took a while to sink in, but yes, you have convinced me. Upgrading is 
    the thing to do, instead of spending time on bugs and performance issues 
    that are fixed in newer cores. I've seen my share of those and it's just 
    not worth the effort to fight these rearguard battles.
    
    It's too bad that upgrading is in many cases a big, complex operation, 
    but that's just the way it is.
    
    Thanks for your insights!
    
    Op 1/5/21 om 9:27 AM schreef Pedro M. Baeza (Tecnativa):
    
    > Hi, Tom,
    
    >
    
    > Each version can have some bugs, but it's better to handle them 
    
    > between more people than let SaaS users or the same partners to 
    
    > notify/fix them. You think it's "safer" to be on a previous version 
    
    > for avoiding such bugs, but the facts are:
    
    >
    
    > - Such a bug is because of your use cases, and it will be found on the 
    
    > version you are using, no matter if outdated or not. Nobody till then 
    
    > may notify it.
    
    > - Odoo is fixing bugs very quickly and without effort by your part on 
    
    > the latest version (or the previous one), as they are committed to 
    
    > "stabilize" that version, but not on very old versions. A note about 
    
    > this: notifying properly a bug is the key for having it solved. You 
    
    > can't expect to have the work done not doing a minimum effort on your 
    
    > part.
    
    > - Bugs can happen even on unsupported versions, so the maintenance 
    
    > cost starts to rise if you need to fix them by yourself and you are 
    
    > introducing regression risks.
    
    > - There are even occasions where the bug is fixed or doesn't apply on 
    
    > higher versions, but you don't have it in an outdated one. See the 
    
    > recent CVE cases and the effort needed by Stefan and Nils.
    
    > - Odoo continues to improve its test suite, and each version has more 
    
    > and more stability/quality.
    
    >
    
    > Other facts about using outdated versions:
    
    >
    
    > - You need to "backport" features that are on higher versions or lack 
    
    > them.
    
    > - Framework evolves, and using an outdated framework makes your 
    
    > development team to require more time to complete the same tasks, or 
    
    > to not have available some tools. Programming in 2020 with the old API 
    
    > or the v8/v9 hybrid for me is horrible.
    
    > - Collaboration possibilities are reduced working on an outdated 
    
    > version, as there are less contributors on them. You can see the same 
    
    > examples on your 7.0 PRs, or even on the 10.0 PRs, that is more 
    
    > recent, but the same unattended.
    
    > - As a complement to the previous one, new contributors push newer 
    
    > versions, not old ones.
    
    > - Underlying libraries and dependencies are outdated as well, with the 
    
    > problems this supposes.
    
    >
    
    > So at Tecnativa we deal with this not having middle positions: all our 
    
    > customers go to latest versions (the supported ones), and we reject 
    
    > those that don't want this approach. That way, we focus on dealing 
    
    > with a reduced set of Odoo versions, we migrate them regularly (not 
    
    > forcing a yearly migration, but more and more customers demand to go 
    
    > to each version and they don't want to keep the same version 2/3 
    
    > years), and we report bugs to Odoo constantly that makes the versions 
    
    > stable enough.
    
    >
    
    > Migrating OCA modules is not a problem while you are on the wheel. The 
    
    > keys are:
    
    >
    
    > - Having a team used to OCA guidelines. All our developments follow 
    
    > strict guidelines. This makes the team to take the habit and don't 
    
    > require more time to be "OCA". Anyway, 95% of our developments are 
    
    > directly OCA. OCA first approach is also very important for us.
    
    > - Having good test coverage. This is vital for easing the migrations. 
    
    > Doing good tests is not easy, but the time spent on that will be for 
    
    > sure gained later. This includes also JS tour/Qunit tests if needed.
    
    > - Reviewing PRs between colleagues as part of your development cycle. 
    
    > This raises a lot your team skills and don't stuck PRs. People 
    
    > complain about their PRs not being reviewed, but they don't review 
    
    > others in exchange or don't push colleagues to review them.
    
    >
    
    > We also take a proactive position for handling some "polemical" 
    
    > decisions taken on the versions, creating OCA modules that fill the 
    
    > gaps. This is better IMO than staying on an older version and 
    
    > complaining that "Odoo has removed this or changed that". In general 
    
    > you win more than you lose on newer versions.
    
    >
    
    > And finally, customers receive a refresh training on each version 
    
    > change. Being proactive as well on the changes they have makes people 
    
    > to not reject the new version and embrace the new features from the 
    
    > beginning.
    
    >
    
    > Do I convince you, hehe?
    
    >
    
    > Regards.
    
    >
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    >
    

    by Tom Blauwendraat - 05:31 - 9 Apr 2021
  • Re: Field Service PSC
    Thank you, Simone, Wolfgang, Maxime, and everyone for these valuable considerations. 
    SANDIP MANGUKIYA
    TEAM LEAD MANAGER
    O: 1.855.877.2377
    E: SMangukiya@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236


    On Tue, Apr 6, 2021 at 11:22 PM Simone Orsi <simahawk@gmail.com> wrote:
    Hi Wolfgang,

    I've added you both. The sync will happen soon.

    Bests,


    On Tue, Apr 6, 2021 at 8:32 PM Wolfgang Hall <whall@opensourceintegrators.com> wrote:
    Dear OCA team, Is this moving forward?

    _________________________________________________
    WOLFGANG HALL
    Director Services Sector
    O: 1.855.877.2377 EXT. 706
    M: 909.754.4549
    E: WHall@OpenSourceIntegrators.com
    1706 PLUM LANE, SUITE 127 • REDLANDS, CA 92374



    On Wed, Mar 31, 2021 at 12:36 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

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



    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, Freelance in love with open source.

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


    by Sandip Mangukiya - 05:10 - 7 Apr 2021
  • Re: Field Service PSC
    Hi Wolfgang,

    I've added you both. The sync will happen soon.

    Bests,


    On Tue, Apr 6, 2021 at 8:32 PM Wolfgang Hall <whall@opensourceintegrators.com> wrote:
    Dear OCA team, Is this moving forward?

    _________________________________________________
    WOLFGANG HALL
    Director Services Sector
    O: 1.855.877.2377 EXT. 706
    M: 909.754.4549
    E: WHall@OpenSourceIntegrators.com
    1706 PLUM LANE, SUITE 127 • REDLANDS, CA 92374



    On Wed, Mar 31, 2021 at 12:36 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

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



    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, Freelance in love with open source.

    by Simone Orsi - 08:20 - 7 Apr 2021
  • Re: Field Service PSC
    I'll do the required changes, they should receive an invitation by 
    tomorrow.
    
    Best regards
    
    Alexandre
    
    On 06/04/2021 20:32, Wolfgang Hall wrote:
    
    > Dear OCA team, Is this moving forward?
    
    > 
    
    > _________________________________________________
    
    > *WOLFGANG HALL
    
    > *Director Services Sector
    
    > *O:* 1.855.877.2377 EXT. 706 <tel:8558772377>
    
    > *M:* 909.754.4549 <tel:9097544549>
    
    > *E:* WHall@OpenSourceIntegrators.com 
    
    > <mailto:whall@opensourceintegrators.com?subject=Email Reply>
    
    > 
    
    > 1706 PLUM LANE, SUITE 127 • REDLANDS, CA 92374
    
    > 
    
    > <https://www.opensourceintegrators.com/>
    
    > 
    
    > 
    
    > 
    
    > 
    
    > On Wed, Mar 31, 2021 at 12:36 PM Maxime Chambreuil 
    
    > <mchambreuil@opensourceintegrators.com 
    
    > <mailto:mchambreuil@opensourceintegrators.com>> wrote:
    
    > 
    
    >     Hello,
    
    > 
    
    >     I would like to propose my 2 colleagues Steve Campbell
    
    >     (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field
    
    >     Service PSC.
    
    > 
    
    >     Thank you and stay safe!
    
    > 
    
    >     *MAXIME CHAMBREUIL*
    
    >     MANAGING DIRECTOR LATAM
    
    >     *O:* 1.855.877.2377 EXT. 710 <tel:8558772377>
    
    >     *M:* 602.427.5632 <tel:6024275632>
    
    >     *E:* MChambreuil@OpenSourcelntegrators.com
    
    >     <mailto:mchambreuil@OpenSourcelntegrators.com?subject=Email Reply>
    
    > 
    
    >     P.O. BOX 940, HIGLEY, AZ 85236
    
    > 
    
    >     <https://www.opensourceintegrators.com/>
    
    > 
    
    >     <https://www.magentointegrators.com/><https://www.hadoopintegrators.com/><https://www.usaodoo.com/>
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    > 
    
    
    
    -- 
    Alexandre Fayolle
    Senior Software Engineer
    Tel : +33 4 58 48 20 30
    
    Camptocamp France SAS
    18 rue du Lac Saint André
    73 370 Le Bourget-du-Lac
    France
    
    http://www.camptocamp.com
    

    by Alexandre Fayolle - 08:15 - 7 Apr 2021
  • Re: Field Service PSC
    Dear OCA team, Is this moving forward?

    _________________________________________________
    WOLFGANG HALL
    Director Services Sector
    O: 1.855.877.2377 EXT. 706
    M: 909.754.4549
    E: WHall@OpenSourceIntegrators.com
    1706 PLUM LANE, SUITE 127 • REDLANDS, CA 92374



    On Wed, Mar 31, 2021 at 12:36 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

    by Wolfgang Hall - 08:31 - 6 Apr 2021
  • Re: package in a package?
    Hi Denis,

    Thanks for your reply, I understand this pick-pack-ship flow,
    I clarify my use case: I have two companies A and B:
    Company A picks products, packs them in several packages, and puts packages on a pallett and ships the pallett to the company B.
    Company B unpacks the pallett, and needs to know the origin package information (stock.move.line A in the package PACK001, stock.move.line in the package PACK002, ...). Maybe naively, I thought that Odoo was going to keep the multi level package information, but it seems that a stock.move.line always goes from an origin package to a destination package.

    Romain



    Le mar. 6 avr. 2021 à 11:32, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
    Hi Romain,

    In your case, it is recommended to do the packings in several operations.

    STOCK =PICKING> |PICK ZONE| =PACK> |PACK ZONE| =SHIP> |CUSTOMERS|

    So, during picking you can put your products in a pack, and in packing operation you can put your packs on a pallet.

    I hope this would help you.


    Regards,

    On Tue, Apr 6, 2021 at 11:12 AM Romain Deheele <romain@avosdim.com> wrote:
    Hello community,

    with standard or OCA Odoo modules, is there the feature to put a stock.move.line in the destination package (like a small unit as parcel/package) and after several minutes to put the same stock.move.line in a bigger unit like a pallet without losing the information that the stock.move.line is both in the package and in the pallet? 
    At use, it seems to me that, by default, a stock.move.line is only in a package at the same time, and not in a package (parcel) which is in a package (pallett).
    Maybe I missed something?

    Regards,

    Romain Deheele

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



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

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


    by romain@avosdim.com - 12:10 - 6 Apr 2021
  • Re: package in a package?
    Hi Romain,

    In your case, it is recommended to do the packings in several operations.

    STOCK =PICKING> |PICK ZONE| =PACK> |PACK ZONE| =SHIP> |CUSTOMERS|

    So, during picking you can put your products in a pack, and in packing operation you can put your packs on a pallet.

    I hope this would help you.


    Regards,

    On Tue, Apr 6, 2021 at 11:12 AM Romain Deheele <romain@avosdim.com> wrote:
    Hello community,

    with standard or OCA Odoo modules, is there the feature to put a stock.move.line in the destination package (like a small unit as parcel/package) and after several minutes to put the same stock.move.line in a bigger unit like a pallet without losing the information that the stock.move.line is both in the package and in the pallet? 
    At use, it seems to me that, by default, a stock.move.line is only in a package at the same time, and not in a package (parcel) which is in a package (pallett).
    Maybe I missed something?

    Regards,

    Romain Deheele

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



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

    by Denis Roussel - 11:31 - 6 Apr 2021
  • package in a package?
    Hello community,

    with standard or OCA Odoo modules, is there the feature to put a stock.move.line in the destination package (like a small unit as parcel/package) and after several minutes to put the same stock.move.line in a bigger unit like a pallet without losing the information that the stock.move.line is both in the package and in the pallet? 
    At use, it seems to me that, by default, a stock.move.line is only in a package at the same time, and not in a package (parcel) which is in a package (pallett).
    Maybe I missed something?

    Regards,

    Romain Deheele

    by romain@avosdim.com - 11:11 - 6 Apr 2021
  • Re: Field Service PSC
    +1

    Le jeu. 1 avr. 2021 à 00:57, Jay Vora <vora.jay@serpentcs.com> a écrit :

    +1
    On Thu, 1 Apr 2021 at 2:07 AM, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    +1
    Bruno Joliveau - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le mer. 31 mars 2021 à 15:42, Maxime Chambreuil <mchambreuil@opensourceintegrators.com> a écrit :
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

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

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

    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


     
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com

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



    --
    Raphaël Reverdy
    Mobile +33 6 38 02 03 93
    Fixe +33 4 82 53 84 60

    by Raphaël Reverdy - 12:01 - 1 Apr 2021
  • Login as Admin like in Odoo.SH

    Hi community,


    Does anyone know how to have a button like in Odoo.SH:
    image.png

    Is that possible to connect as a certain user? I get a session token then use it as a Header?

    Thanks!


    by Diogo Duarte - 11:31 - 1 Apr 2021
  • Re: Field Service PSC

    +1
    On Thu, 1 Apr 2021 at 2:07 AM, Bruno Joliveau <bruno.joliveau@numigi.com> wrote:
    +1
    Bruno Joliveau - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le mer. 31 mars 2021 à 15:42, Maxime Chambreuil <mchambreuil@opensourceintegrators.com> a écrit :
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

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

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

    --

    Technology Services @ www.serpentcs.com
    Business Solutions @ www.serpentcs.in
    Enterprise Mobile Apps @ www.odooonline.com 
    Quality Assurance @ www.odooqa.com
    Portal & DMS @ www.alfray.in



    Regards,
    ----------------------------------------------------------------------------------------------------------------------------
    Jay Vora
    Managing Director


     
    Direct: +91-9879354457
    Office: +91-9033472982
    Skype: jaynvora
    Twitter : jaynvora
       
    -------------------------------------------------------------------------------------------------
    Visit our website : http://www.serpentcs.com


    by Jay Vora - 12:56 - 1 Apr 2021
  • Re: Field Service PSC
    +1
    Bruno Joliveau - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter


    Le mer. 31 mars 2021 à 15:42, Maxime Chambreuil <mchambreuil@opensourceintegrators.com> a écrit :
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

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


    by Bruno Joliveau - 10:36 - 31 Mar 2021
  • Re: Field Service PSC
    I second that.
    _________________________________________________
    WOLFGANG HALL
    Director Services Sector
    O: 1.855.877.2377 EXT. 706
    M: 909.754.4549
    E: WHall@OpenSourceIntegrators.com
    1706 PLUM LANE, SUITE 127 • REDLANDS, CA 92374



    On Wed, Mar 31, 2021 at 12:36 PM Maxime Chambreuil <mchambreuil@opensourceintegrators.com> wrote:
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

    by Wolfgang Hall - 10:11 - 31 Mar 2021
  • Re: Field Service PSC
    +1

    El mié., 31 mar. 2021 21:42, Maxime Chambreuil <mchambreuil@opensourceintegrators.com> escribió:
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

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


    by Pedro M. Baeza - 09:56 - 31 Mar 2021
  • Re: Field Service PSC
    +1

    On Wed, 31 Mar 2021, 1:42 pm Maxime Chambreuil, <mchambreuil@opensourceintegrators.com> wrote:
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

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


    by Patrick Wilson - 09:56 - 31 Mar 2021
  • Field Service PSC
    Hello,

    I would like to propose my 2 colleagues Steve Campbell (osi-scampbell) and Sandeep Mangukiya (smangukiya) to join the Field Service PSC.

    Thank you and stay safe!

    MAXIME CHAMBREUIL
    MANAGING DIRECTOR LATAM
    O: 1.855.877.2377 EXT. 710
    M: 602.427.5632
    E: MChambreuil@OpenSourcelntegrators.com
    P.O. BOX 940, HIGLEY, AZ 85236

    by Maxime Chambreuil - 09:41 - 31 Mar 2021
  • Re: Odoo load balancing
    HAProxy?

    Verstuurd vanaf mijn iPhone

    Op 31 mrt. 2021 om 12:27 heeft Tom Blauwendraat <tom@sunflowerweb.nl> het volgende geschreven:

    

    Hi community,

    I'm looking for advice and experience regarding the topic of load balancing.

    There are two unrelated cases in which I would like to use it:

    1. Balancing over a pool of servers running Odoo

    We have a client with a horizontal setup with a pool of 4 servers running Odoo. Requests are now routed to the servers by means of round-robin, but that's not very smart - I'd rather pass the load to the server that I know has enough free workers, and perhaps memory/CPU/IO available to take on a new task. I've looked around and the only thing I've found so far is the UWSGI FastRouter: https://uwsgi-docs.readthedocs.io/en/latest/Fastrouter.html. Does someone have other suggestions?

    2. Smart balancing over worker pools on one server

    For a responsive Odoo you want to have many Odoo workers, but you don't want to run out of memory. This is a tradeoff. If you configure too few workers, your memory will sit idle, but if you configure many workers, you run the risk that occasional high memory requests (a heavy computation, a heavy report) come in and if by unlucky chance it's several at a time, your server can overload. Is there a load balancer or WSGI application server that can keep a track record of which requests generally take the most memory, and then throttle these requests to a limited "heavy pool" of Odoo workers that serve high-memory requests, whereas the "happy pool" will have many workers and process the trustworthy requests with much better responsiveness?

    Sorry if this is not the right place to ask - I will be happy about any pointers.

    -Tom

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


    by Willem Hulshof - 08:56 - 31 Mar 2021