Rootconf 2017

On service reliability

##Submit proposals for flash talks
Rootconf is on 11-12 May. If you have:

  1. Tips and tricks for simplifying infrastructure management and maintenance;
  2. Experiences with new tools to share;
  3. Cool demos;

then propose a flash talk here, or on the spot, at the venue.

The flash talk session is on 11 May, from 17:20-18:20. We have room for about 12 flash talks. Each presentation should be no more than 5 minutes.

A final note of caution when presenting at flash talks: we have a code of conduct at the conference. You must refrain from making remarks that may be perceived as sexist or derogatory. If you want to double check your presentation, contact Sandhya Ramesh, Karthik B. or Zainab Bawa at the venue.

The theme for the 2017 edition is service reliability. The conference will feature talks on state of the art deployment strategies and appropriate monitoring technologies at different scales. Rootconf this year will broadly cover topics like toil, on-call, outage handling, and post-mortem analysis. We are inviting presentation proposals from academics and practitioners on these topics.

Rootconf aims to appeal to the widest possible range of DevOps practitioners: from embryonic startups to the largest established enterprises. We are keen to schedule presentations that appeal both to attendees’ current needs as well as their future aspirations.

##About the Conference
Rootconf is India’s principal conference where systems and operations engineers share real world knowledge about building reliable systems. We are now accepting submissions for our next edition which will take place in Bangalore on 11-12 May 2017.

Topics for Round 2 of the CfP were:

  1. Capacity planning.
  2. Deploying microservices, and issues concerning monitoring and reliability of microservices.
  3. Deployment and orchestration of container based infrastructures.
  4. Open tracing.

Topics for Round 1 of the CfP were:

  1. Monitoring strategies
  2. Deployment strategies
  3. Capacity planning
  4. Automation beyond deployment and monitoring
  5. Eliminating toil
  6. On-call outage handling
  7. Postmortem / root cause analysis
  8. Incident response

Rootconf is a three track conference:

We are inviting proposals for:

  • Full-length 40-minute talks – which cover conceptual topics and include case studies.
  • Crisp 15-minute how-to talks or introduction to a new technology.
  • Sponsored sessions, of 15 minutes and 40 minutes duration (limited slots available; subject to editorial scrutiny and approval).
    Hands-on workshop sessions of 3 and 6 hour duration where participants follow the instructors on their laptops.

##Selection Process
Proposals will be filtered and shortlisted by an Editorial Panel. Please make sure to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience and delivery style. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals. We might contact you to ask if you’d like to repost your content on the official conference blog.

We expect you to submit an outline of your proposed talk, either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.

Selection Process Flowchart

You can check back on this page for the status of your proposal. We will notify you if we either move your proposal to the next round or if we reject it. Selected speakers must participate in one or two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.

A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.

There is only one speaker per session. Entry is free for selected speakers.

##Travel Grants
As our budget is limited, we prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek provides these limited grants where applicable:

  • Two grants covering travel and accommodation for international speakers.
  • Three grants covering travel and accommodation for domestic speakers.

Grants will be made available to speakers delivering full sessions (40 minutes or longer).
*Speaker travel grants will be given in the order of preference to students, women, persons of non-binary genders, and speakers from Asia and Africa.

##Commitment to Open Source
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a “sponsored session”.

##Important Dates:

  • Deadline for submitting proposals: 10 April, 2017
  • Final conference schedule: 15 April 2017
  • Conference dates: 11-12 May, 2017

For more information about speaking proposals, tickets and sponsorships, contact or call +91-7676332020.

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more

Nitin Mehra


Performance Monitoring for single page applications.

Submitted Feb 15, 2017

As the world is moving more and more towards javascript enabled applications, its becoming increasingly complex to define performance of online web applications. The typical page load time metric has proven to be unsuitable and has been replaced with other more suitable metrics like first paint and time to interactive. In this talk I would like the listeners to understand how we can measure performance of these single page applications, what are the prevailing metrics that make sense. I will dive deeper into a simple framework that can be developed inhouse to get measure, report and alert based on these metrics. In the end i would also like to go over a simple evaluation of some of the existing tools.


At the end of this talk listeners would be able to understand:
1.What is web performance monitoring and why it is important?
2.What are some of the important metrics that should be captured for Single page applications?
3.How can we develop/reuse a simple framework to measure these metrics?
4.Other tools that are available which can help us in measuring.
In the first few slides listeners will understand the different kinds of performance monitoring methodologies namely:
1.What is Synthetic monitoring and how it is typically implemented?
2.What is Real time performance monitoring and how it is implemented?
Why is Real time performance monitoring equally or more important than just using synthetic monitoring?
In the next 2-3 slides we will go over the importance of reporting performance data in percentiles instead of calculating averages.
We will also describe how page load times are misleading in the world of javascript apps and describe some of the relatively new metric terms like time to first paint and time to user interactive metrics have gained importance.
In the next few slides we will go over how the browser (using navigation timing, user timing and resource timing) enables us today to take these measurements.
At this time we will get into the details of building a framework which will allow the development team to measure the metrics described above using the api’s provided by the browser. We will briefly go over the algorithm that is used for
•fresh page load: (last executed user marker – navigation start)
•button click: [last executed user marker (for route change, ajax, js)- user marker (setup for click/route change)]
•Send data using a beacon.
Showcase some of the reports generated for RUM for performance
Describe shortcomings to this approach namely:
•Developers need to keep track of markers
We can define some extensions to this approach:
•Run a preprocessing module with an input(describing the workflow) to capture the render of sections that are above the fold and DOM mutations that take place because of ajax/user clicks.
•Put user timing markers at certain sections in the source code during the build step using a processing module. (described above)
•Including a javascript file (for the algorithm described above) which will be used to capture metrics.
Finally we will cover an evaluation of some tools that help in real user performance monitoring for single page applications.

Speaker bio

I’m a staff engineer at Intuit working in the e-commerce domain. I have been involved in the building of performant online applications.
I have worked on front-end architectures be it on migrating to Single page (javascript) applications, their performance or seo content generation for single page applications. At the same time I have also worked on the backend services from designing them to improving their performance, to monitoring them while in production.



{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

Rootconf is a community-funded platform for activities and discussions on the following topics: Site Reliability Engineering (SRE). Infrastructure costs, including Cloud Costs - and optimization. Security - including Cloud Security. more