how to access data and maintain adequate time responses as the amounts of data gathered escalate. This depends to a great extent on the database optimization, but also on the number of visualizations offered by default. Talaia relies on a Mysql database. The interface does not access data from the actual tables, but rather from a joint view which is refreshed periodically. This reduces the time response from minutes to seconds [^23]

Success Cases {#isv2018:success}
=============

In this section we present two real use cases where Talaia has been applied, and use them for evaluation purposes. The first one focuses on tracking cultural events. The second one analyses citizen opinions with respect to political parties and candidates during an electoral campaign.

Both monitoring processes presented here ran on their own dedicated servers. We provide details on hardware specifications and volumes of data processed in the following subsections. As a measure of the performance capabilities of our system, the largest monitoring process we have carried out until now gathered 24M tweets per month, with an average of 700K tweets processed per day and a maximum of 1.35M tweets in a single day. Talaia ran on a server with two Intel Xeon 