CEDEC2017「優れãŸã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ãŒé›†ã¾ã‚Šç¶™ç¶šçš„ã«æˆé•·ã™ã‚‹ä¼šç¤¾ã«ã™ã‚‹æ–¹æ³• ～組織を急拡大ã•ã›ã‚‹æŽ¡ç”¨è‚²æˆè©•ä¾¡ã‚¬ã‚¤ãƒ‰ï½žã€è¬›æ¼”資料ã§ã™ã€‚
優れãŸã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ãŒé›†ã¾ã‚Šç¶™ç¶šçš„ã«æˆé•·ã™ã‚‹ä¼šç¤¾ã«ã™ã‚‹æ–¹æ³• ～組織を急拡大ã•ã›ã‚‹æŽ¡ç”¨è‚²æˆè©•ä¾¡ã‚¬ã‚¤ãƒ‰ï½ž/Concise Guide to Finding the Best Technical Talent
CEDEC2017「優れãŸã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ãŒé›†ã¾ã‚Šç¶™ç¶šçš„ã«æˆé•·ã™ã‚‹ä¼šç¤¾ã«ã™ã‚‹æ–¹æ³• ～組織を急拡大ã•ã›ã‚‹æŽ¡ç”¨è‚²æˆè©•ä¾¡ã‚¬ã‚¤ãƒ‰ï½žã€è¬›æ¼”資料ã§ã™ã€‚
ActiveRecord Sharding
å‰å›žã®ç¶šã ActiveRecordãŒå®Ÿéš›ã«DBã«ã‚¯ã‚¨ãƒªã‚’発行ã™ã‚‹å ´åˆActiveRecord::Base.connectionを経由ã™ã‚‹ã€‚話をå˜ç´”ã«ã™ã‚‹ç‚ºã«ã€ã‚¯ã‚¨ãƒªã®å®Ÿè¡Œã ã‘ã«é™å®šã—ã¦Shardingを実ç¾ã—よã†ã¨æ€ã£ãŸå ´åˆã“ã®ãƒ¡ã‚½ãƒƒãƒ‰ãŒãã‚Œãžã‚Œã®Shardã«å¯¾ã—ã¦ç¢ºç«‹ã•ã‚ŒãŸã‚³ãƒã‚¯ã‚·ãƒ§ãƒ³ã‚’è¿”ã›ã°è‰¯ã„。 一番多ã採用ã•ã‚Œã¦ã„る実ç¾æ–¹æ³•ã¯connectionメソッドを上書ãã—ã¦proxyを経由ã•ã›ã‚‹ãƒ‘ターンã§ã€å¤šãã®Gemã§æŽ¡ç”¨ã•ã‚Œã¦ã„る。ãã®ä»–ã«ã‚‚コãƒã‚¯ã‚·ãƒ§ãƒ³ã®ç¢ºç«‹æ–¹æ³•ãƒ»ç®¡ç†ãªã©ã§æ—¢å˜ã®GemãŒã©ã†ã‚„ã£ã¦å®Ÿç¾ã—ã¦ã„ã‚‹ã‹ã‚’ã„ãã¤ã‹ç´¹ä»‹ã™ã‚‹ã€‚ Octopus ãŠãらã一番有åãªã®ã‹ã‚‚ã—ã‚Œãªã„Gem。kovyrin/db-charmerã®å½±éŸ¿ã‚’å°‘ãªã‹ã‚‰ãšå—ã‘ã¦ã„る。 実際ã«ç½®ãæ›ãˆã¦ã„ã‚‹ã®ã¯ã€ActiveRecord::Baseã«Octopus::Modelã‚’extendã—ãŸéš›ã«å®Ÿè¡Œã•ã‚Œã‚‹hij
ActiveRecord Connection
ActiveRecordã®Shardingライブラリをè¨è¨ˆã™ã‚‹éš›ã«ã€å¯¾å¿œã™ã‚‹å¿…è¦ãŒã‚るコãƒã‚¯ã‚·ãƒ§ãƒ³ç®¡ç†ã¨å®Ÿéš›ã«ã‚³ãƒã‚¯ã‚·ãƒ§ãƒ³ãŒã©ã®ã‚ˆã†ã«ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹ã®ã‹ã®éƒ¨åˆ†ã«ã¤ã„ã¦æ›¸ãç•™ã‚ã¦ãŠã。 対象ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯4.2.4ã ã‘ã©4ç³»ãªã‚‰å¤§ä½“åŒã˜ãªã®ã§å•é¡Œãªã„ã¨æ€ã†ã€‚ データベースã¸ã®æŽ¥ç¶šã¯initializerã§è¡Œã‚れる。 # active_record/railtie.rb initializer "active_record.initialize_database" do |app| ActiveSupport.on_load(:active_record) do self.configurations = Rails.application.config.database_configuration begin establish_connection rescue ActiveRecord:
Azureã€AWS を使ã£ã¦ä¸å¹¸ã«ãªã£ã¦ã„る方々ã¯ä»Šã™ã GCP を使ã†ã¨å¹¸ã›ã«ãªã‚Œã‚‹ - クラウド㯠GCP 一択 - å¼·ã¾ã£ã¦ã„ã“ã†
シリアルコンソール接続ãŒç„¡ã„クラウドãªã‚“ã¦ã‚´ãƒŸã ã¨æ€ã£ã¦ã„ã¾ã™ã€‚ã©ã†ã‚‚皆ã•ã‚“ã€å…ƒæ°—ã§ã™ã‹ã€åƒ•ã§ã™ã€‚ AWSã€Azure ã§ä½•ã‹ã—らトラブルãŒèµ·ã“ã‚‹ã¨å®Œå…¨ã«è©°ã‚€ã‚“ã§ã™ã‚ˆãã€ã‚³ãƒ³ã‚½ãƒ¼ãƒ«æŽ¥ç¶šãŒç„¡ã„ã°ã‹ã‚Šã«ã€‚ èµ·å‹•ã«å¤±æ•—ã—ãŸã‚‰ã€ã‚‚ã†ã‚µãƒãƒ¼ãƒˆã‚»ãƒ³ã‚¿ãƒ¼è¡Œãã§ã™ã‚‚ã®ã€‚AWSã€Azure ã©ã¡ã‚‰ã¨ã¯è¨€ã„ã¾ã›ã‚“ãŒã€ã‚µãƒãƒ¼ãƒˆã¨ä½•æ™‚é–“ã‚‚ã‚„ã‚Šå–ã‚Šã—ãŸçµæžœã€ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’コピーã—ã¦ã€VM を作り直ã—ã¦ãã‚Œã€ãªã‚“ã¦ã“ã¨è¨€ã‚れるんã§ã™ã‚ˆã€‚ ゴミã¿ãŸã„ã«å‘ªã‚ã‚ŒãŸã€ã©ã†é ã‚’ã“ã˜ã‚‰ã›ãŸã‚‰ã“ã‚“ãªã‚‚ã®ä½œã‚Œã‚‹ã‚“ã ？ã¨é–‹ç™ºè€…ã®è„³ã¿ãã®å‡ºæ¥ã‚’ç–‘ã†äººé¡žå²ä¸Šæœ€ä½Žã® Shellã€Power Shellã‚’å©ãã¾ãã‚‹ã“ã¨ã«ãªã‚‹ã‚“ã§ã™ã‚ˆã€‚ã‚ã€ã©ã£ã¡ã‹ãƒãƒ¬ãŸã€‚ GCP ã«ã¯ã‚³ãƒ³ã‚½ãƒ¼ãƒ«æŽ¥ç¶šãŒã‚ã‚Šã¾ã™ã€‚iptables ã§å¤‰ãªè¨å®šã‚’入れ㦠SSH ãŒåˆ‡æ–ã•ã‚ŒãŸã¨ã—ã¦ã‚‚ã€ã©ã†ã«ã§ã‚‚ãªã‚Šã¾ã™ã€‚ 昔ã¯ã•ãらインターãƒãƒƒãƒ„ã«ã‚‚コンソール接続ãŒãªãã¦ã€Œå†èµ·å‹•ã—ã¦ãã
The relationship between Innodb Log checkpointing and dirty Buffer pool pages
This is a time-honored topic, and there’s no shortage of articles on the topic on this blog. I wanted to write a post trying to condense and clarify those posts, as it has taken me a while to really understand this relationship. Some basic facts Most of us know that writing into Innodb updates buffer pool pages in memory and records page operations in the transaction (redo) log. Behind the scenes
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}