-
Notifications
You must be signed in to change notification settings - Fork 13
Postgres Testing
Charlie Martin edited this page Feb 1, 2016
·
2 revisions
I spent some time bringing up a Postgres version of CHORDS on my MacBook Pro. It's in the pg branch. There were a few MySQL/Postgres differences that required code changes.
The main point was to see if Postgres gave better performance than MySQL. There didn't seem to be any improvements at all. This was true before and after the dashboard_helper refactor.
I also experimented with changing some recommended Postgres database configuration parameters:
- Changed shared_buffers to 1024MB
- Changed work_mem to 1024B
- Enabled all of the query tuning options
None of these made any difference in the dashboard rendering time.
Project Management
- Stakeholders
- Communication
- Use Cases
- Requirements
- Deliverables
- Milestones Associated with a Release
- "Sandbox" Milestones
- Github Workflow
AWS
- AWS Portal Migrations
- Amazon Appliance Workflow
- Overview
- Bringing up a new CHORDS Portal
- Cloud Formation
- EC2 Costing and Memory Constraints
Docker
- Running CHORDS
- Docker on AWS
- Duplicating Docker/Influxdb portals
- Docker on Raspberry Pi
- Docker Details and Tips
- Running CHORDS on Windows 10
Influxdb
Data Formats
Google Maps
Ingest Utilities
Miscellaneous
- Recovery from a full disk
- Github/Dockerhub release scheme
- CHORDS gh-pages and jeykll
- Bootstrap
- CHORDS Portal Web Site
- Dashboard Helper Refactor
- Development Notes
- Heroku
- Meteobridge
- Migrating from mysql to mysql/influxdb portals
- NCAR Wx Stations into CHORDS
- PAWS to CHORDS
- Post Get Query Syntax
- Postgres Testing
- Rails Tips
- Ruby and Rails Resources
- CUAHSI Archive
Historical Archive