Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write blog post of current technology stack of Waartaa #4

Open
rtnpro opened this issue May 15, 2014 · 0 comments
Open

Write blog post of current technology stack of Waartaa #4

rtnpro opened this issue May 15, 2014 · 0 comments
Assignees

Comments

@rtnpro
Copy link
Member

rtnpro commented May 15, 2014

  • proposed title: "Anatomy of Waartaa 0.1"
  • Shortcomings of 0.1-rc-1
    • Not at all scalable
    • High resource utilization by app and mongodb
    • Too many read/writes to mongodb
  • Solution
    • Upgrade to Meteor's OPLOG driver from 0.8 release (with support for complex queries)
    • Minimize writes to MongoDB:
      • write channel log once per server channel irrespective of the number of active waartaa users on the channel
      • minimize writes to add/remove a channel nick
      • Reduce storage complexity of logs. Storage complexity now depends on only the number of active channels and is irrespective of the number of active waartaa users.
  • Async write to mongodb optimized app performance and brought down CPU usage
  • The way ahead:
    • Run IRC server as a different service, and allow multiple instances of it for horizontal scaling.
    • Run multiple instance of waartaa's app server.
@rtnpro rtnpro self-assigned this May 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant