Hi Steph, I suspect that Jetty is leaking some resource, and we may need to upgrade it.
Karl On Tue, Sep 4, 2018 at 11:26 AM Steph van Schalkwyk <[email protected]> wrote: > Olivier > By all means. > The only issue I have seen (totally unrelated) is with Jetty, which has to > be restarted about once a week. Still trying to find the issue. > I may be overly sensitive, but I suspect MCF 2.10 with Postgres10 may be a > bit slower. I have no empiric evidence at the moment as I'm still > delivering the project to UAT. Will keep you posted. > Regards, > Steph > > > > *Steph van Schalkwyk* > Principal, Remcam Search Engines > +1.314.452. <+1+314+452+2896>2896 [email protected] http://remcam.net > <http://www.remcam.net/> Skype: svanschalkwyk > <https://mail.google.com/mail/u/0/#> > <http://linkedin.com/in/vanschalkwyk> > > On Tue, Sep 4, 2018 at 9:59 AM, Olivier Tavard < > [email protected]> wrote: > >> Hello, >> >> Thanks a lot for sharing your PostgreSQL configuration (sorry for the >> late answer). I will test it soon. >> >> Best regards, >> >> >> Olivier TAVARD >> >> >> Le 23 août 2018 à 19:20, Steph van Schalkwyk <[email protected]> a écrit : >> >> >> >> These are the rpm installs: >> - file:///tmp/postgres10/postgresql10-libs-10.4-1PGDG.rhel7.x86_64.rpm >> - file:///tmp/postgres10/postgresql10-10.4-1PGDG.rhel7.x86_64.rpm >> - file:///tmp/postgres10/postgresql10-contrib-10.4-1PGDG.rhel7.x86_64.rpm >> - file:///tmp/postgres10/postgresql10-devel-10.4-1PGDG.rhel7.x86_64.rpm >> - file:///tmp/postgres10/postgresql10-server-10.4-1PGDG.rhel7.x86_64.rpm >> >> postgresql_version: 10 >> postgresql_data_dir: /var/lib/pgsql/10/data >> postgresql_bin_path: /usr/pgsql-10/bin >> postgresql_config_path: /var/lib/pgsql/10/data >> postgresql_daemon: postgresql-10.service >> postgresql_packages: >> - postgresql10-libs >> - postgresql10 >> - postgresql10-server >> - postgresql10-contrib >> # - postgresql10-devel >> >> postgresql_hba_entries: >> - { type: local, database: all, user: postgres, auth_method: peer } >> - { type: local, database: all, user: all, auth_method: peer } >> - { type: host, database: all, user: all, address: '127.0.0.1/32', >> auth_method: md5 } >> - { type: host, database: all, user: all, address: '::1/128', auth_method: >> md5 } >> - { type: host, database: all, user: all, address: '0.0.0.0/0', >> auth_method: md5 } >> - { type: host, database: all, user: all, address: '::0/0', auth_method: >> md5 } >> >> postgresql_global_config_options: >> - option: unix_socket_directories >> value: '{{ postgresql_unix_socket_directories | join(",") }}' >> >> - option: standard_conforming_strings >> value: 'on' >> >> - option: shared_buffers >> value: '1024MB' >> >> # max_wal_size = (3 * checkpoint_segments) * 16MB >> # checkpoint_segments=300 >> - option: max_wal_size >> value: '14400MB' >> >> - option: min_wal_size >> value: '80MB' >> >> - option: maintenance_work_mem >> value: '2MB' >> >> - option: listen_addresses >> value: '*' >> >> - option: max_connections >> value: '400' >> >> - option: checkpoint_timeout >> value: '900' >> >> - option: datestyle >> value: "iso, mdy" >> >> - option: autovacuum >> value: 'off' >> >> # vacuum all databases every night (full vacuum on Sunday night, lazy >> vacuum every night) >> - name: add postgresql cron lazy vacuum >> cron: >> name: lazy_vacuum >> hour: 8 >> minute: 0 >> job: "su - postgres -c 'vacuumdb --all --analyze --quiet'" >> - name: add postgresql cron full vacuum >> cron: >> name: full_vacuum >> weekday: 0 >> hour: 10 >> minute: 0 >> job: "su - postgres -c 'vacuumdb --all --full --analyze --quiet'" >> # re-index all databases once a week >> - name: add postgresql cron reindex >> cron: >> name: reindex >> weekday: 0 >> hour: 12 >> minute: 0 >> job: "su - postgres -c 'psql -t -c \"select datname from pg_database >> order by datname;\" | xargs -n 1 -I\"{}\" -- psql -U postgres {} -c >> \"reindex database {};\"' " >> >> >> This is how I run 2.10. >> Been running fine for some weeks without user intervention. >> @Karl: Any comments please? >> Steph >> >> >> >> >
