content/news/2012-04-06-database-prune.md

   1 ---
   2 author: Martinp23
   3 date: 2012-04-06 20:33:38+00:00
   4 slug: database-prune
   5 title: Database prune
   6 category: community
   7 category: development
   8 category: freenode
   9 category: infrastructure
  10 category: technical
  11 imported: yes
  12 ---
  13 Every couple of years, freenode likes to get out the shears and prune the services database. Recently we broke the 80,000 usercount barrier, but the services stats are way ahead:
  14
  15 > Sat 13:35:46 -OperServ(OperServ@services.)- Registered accounts: 446777<br>
  16 > Sat 13:35:46 -OperServ(OperServ@services.)- Registered nicknames: 557497<br>
  17 > Sat 13:35:47 -OperServ(OperServ@services.)- Registered channels: 141373<br>
  18
  19 We've noticed that nearly half of the accounts shown there haven't been used in
  20 the past 6 months! More importantly, over the past few months many people have
  21 noticed significant waits when issuing certain services commands - and we'd
  22 like to fix that.
  23
  24 Hopefully, the [services
  25 upgrade](http://blog.freenode.net/2012/04/help-us-test-our-services-upgrade/)
  26 should help with this, but we're going to coincide this with a database prune.
  27
  28 As of the services upgrade date, any nicks unused for > 150 days are at risk of
  29 being dropped. This includes grouped nicks. The easy way to avoid this
  30 happening is to use each of your grouped nicks (while identified to the
  31 appropriate account) within the next few weeks - and to drop those that you
  32 don't need anymore!
  33
  34 The testnet (testnet.freenode.net, port 9002. 9003 for SSL) is running a
  35 database snapshot from mid-March and will be periodically updated from the
  36 production network. This database instance is being regularly pruned - so check
  37 there to see how your account will be affected (use /msg nickserv info on both
  38 the production and test networks to see the differences).
  39
  40 Remember that testnet isn't running a real-time duplicate of the production
  41 network, so when you use nicks which would be expired on the production
  42 network, they will still appear expired on testnet until the next database
  43 snapshot is migrated. Don't worry though - the actual pruning will only occur
  44 on the current database at the time of upgrade.
  45
  46 On which note.. an upgrade date hasn't been formally fixed but we're aiming for
  47 mid-May.
  48
  49 Thanks, and don't forget to [test the
  50 testnet](http://blog.freenode.net/2012/04/help-us-test-our-services-upgrade/)!