Oh baby it’s a wild world… wide web

We are glad to announce that we have taken yet one more step towards user satisfaction.

Providing a secure web browsing experience is key to protect our users data. That is why from April 2018, streema.com and all its subdomains are secure sites encrypted with HTTPS.

HTTPS encryption ensures that users can access streema.com and enter private information like passwords without anyone intercepting their information. Moreover, even if users do not share any sensitive information, intruders can exploit unprotected websites to potentially reveal information about the behaviors and identities of their users. HTTPS helps prevent intruders from exploiting the communications between websites and users’ browsers.

From now on, Streema’s users are protected by HTTPS encryption even if they type “http://streema.com”, since they will be redirected to the secure HTTPS site.


At Streema we are committed to building better and safer products for our users, while contributing in making the Internet safer for everyone. We are proud to be joining forces with thousands of websites in achieving this mission and we’ll continue working hard to bring our users the experience they deserve.

Stay tuned!
The Streema Team

Improving Radio Player Performance at Streema

Following the improvements we mentioned in our previous blog post, now we’re back with more news about our player – after all, Streema is about playing radio and TV. 🙂

Before we start, something important to mention is that, as we’ve explained before, Streema does not provide the streaming service, but rather it provides the platform for tuning in to stations. However, in many cases we’re not able to play a radio or TV station because there’s a broken stream or because we don’t find compatible players. Here are some figures to explain that better:

For our Radio Desktop users*, last month (August 2013) 70.3% of them were able to play a radio station, while that number was only 57.6% a year ago (August 2012).

*These figures do not include external players – if they did,
the percentage of successful tune ins would be much higher.

 

To do so, a big part of the work was fixing and updating thousands of streams. Additionally, we have also improved how the plugins work as well as the number of plugins supported – for example, last year 13.4% of our users couldn’t play a station because a of plugin compatibility issue, today that number is only 6.1%.

As you might know, a plugin is a software that allows, in our case, to play a station in your browser, so part of our job is to find plugins that will make the audio and video work on your desktop, tablet, or smartphone.

All this has been the result of both testing and measuring better as well as understanding the behavior of our users. Thanks for listening and watching!

Hopefully in the not so distant future we’ll have a chance to share some data regarding mobile as well as TV.

Stay tuned!

The Streema Team

99.88% of Uptime during the past 12 months

This is yest another quick update to let you know we have accomplished an important milestone:

Our website Streema.com has had an Uptime of 99.88% over the past year

This is the result of the work we started in early 2012 when we realized that we had a lot to improve in the areas of Uptime as well as Response Time.

So, even though our Uptime numbers aren’t perfect – since we still had in total over 10 hours of downtime in 365 days – we still wanted to share this value with you since we know it’s appreciated amongst our users.

Regarding the other area, Response Time, we haven’t made as much progress in the last year, but we promise to have good news in the next report. 😉

Stay tuned,

The Streema Team

Improving Testing Time at Streema

At Streema we like to develop at a fast pace.  One of the things that allows us to do that is to have an automatically tested codebase. We want to always be shipping and having our apps tested gives us some degree of confidence that we won’t break it all each time we commit a change.

But running tests takes time. A few months ago our unit tests were taking over 12 minutes to run. Each time someone wanted to run the tests, the situation was pretty much like this:

As you might recall, we use Python/Django. And our problem was the use of fixtures in our unit/functional tests. As @carljm said on his “Testing and Django” talk for PyCon 2012, they are slow to load, hard to maintain and increase test interdependence. We had huge fixtures, 1mb fixtures, which loaded thousands of models and they were used on dozens of tests!  With a little bit of patience we were able to remove them all and replace them by using factory boy.

The result:  we reduced the test run time from over 12 minutes to under a minute.  Yes, a single minute.  =)

Stay tuned for more news and insight on the technical details of Streema. We might have an interesting thing or two to share!

Stay tuned!

The Streema Team

Improving Uptime and Performance on Streema

Starting late last year, at Streema we’ve been working hard to improve the website’s uptime and performance – nothing is more annoying than a tech service or device when it doesn’t respond, right?

So we wanted to give you guys a quick update on this, but before we start, though, two important definitions:

Response Time: The interval between a request that enters and the answer that is received. In this case it’s the page load time, i.e. the time to retrieve the HTML page (without images, stylesheets, JavaScript, etc.). So, although it could be below a hundred ms (milliseconds), as a user, it could translate into seconds to load a complete page.

Downtime: It is the period when the system is unavailable, i.e. the period you wait, mostly doing nothing, and if it goes above what you expected, you start hitting your computer or anything around you, in addition to shouting out phrases such as “come on!”, “ahhhh” or others that we can’t publish right here. 🙂

So, we’re happy to share with you that we’ve reduced our Response Time almost by a half and the number of Downtimes by about 75%. Even better, some of the Downtimes we had before took hours, now they are less than 10 minutes – additionally, now they only happen because of our own updates to our site and not because of infrastructure problems!

For those techies out there, here’s a quick summary of what we’ve been doing to get results:

  • Increase the number of servers and balance the load with Nginx.
  • Improve the database setup to take advantage of the servers memory.
  • Rewrite many SQL queries, specially the ones that requested temporal tables on the hard drive.
  • Change the configuration of the Apache modwsgi and increase the number of processes to serve requests.

Finally, regarding the tools we’ve been using, the main ones were: Apache’s Server Status, Munin, New Relic, Percona Tools and Pingdom.

We’re planning to continue developing our performance infrastructure – and we hope you continue visiting Streema. 🙂

Stay tuned!

The Streema Team