Nathan Wilson mo-nathan

## 2018-12-rails-5.0-upgrade
Goals based on upgrade page: https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-4-2-to-rails-5-0

4.1 Ruby version: We're already good at 2.4.  Might consider going to 2.5, but no urgency.

4.2 Introduce ApplicationRecord.
- Search for ActiveRecord::Base.
- Ensure that all classes inherit from ApplicationRecord
- Add definition per web page

4.3 Halting Callback Chains: Don't think this is relevant to anything we're doing, but we'll see.

## 2018-11-db-upgrade-impact.md

      
              1 file
            
          
              0 forks
            
          
              2 comments
            
          
              1 star
            
          
                mo-nathan
                / 2018-11-db-upgrade-impact.md
            
            
              Last active
              November 30, 2018 12:30
            
          
    Sunday November 11, 2018 the Mushroom Observer database server was upgraded from 4 CPU cores to 6 CPU cores
and the available RAM was doubled.
Around November 22, Alan Rockefeller analysed the logs to see what the impact was.  He compared the previous week
to the entire month of October 2018 and found:
Average time to respond to requests pre-upgrade: 2.29117 seconds (every request in October averaged)
Average time to respond to requests post-upgrade: 1.57632 seconds (every request in the past week averaged)

  
## Verifying my Peepeth
Verifying my identity on Peepeth.com 0x2bc3be1b716e03c62bdd36d8ebdc1fb4a17c2fc3
	Goals based on upgrade page: https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-4-2-to-rails-5-0

	4.1 Ruby version: We're already good at 2.4. Might consider going to 2.5, but no urgency.

	4.2 Introduce ApplicationRecord.
	- Search for ActiveRecord::Base.
	- Ensure that all classes inherit from ApplicationRecord
	- Add definition per web page

	4.3 Halting Callback Chains: Don't think this is relevant to anything we're doing, but we'll see.