Hi, Qiming Teng.

Now all backends support events. So you may use MongoDB instead of
MySQL, or if you like you may choose HBase.

Cheers, Igor.
-- Igor


On Thu, Sep 25, 2014 at 7:43 AM, Preston L. Bannister
<pres...@bannister.us> wrote:
> Sorry, I am jumping into this without enough context, but ...
>
>
> On Wed, Sep 24, 2014 at 8:37 PM, Qiming Teng <teng...@linux.vnet.ibm.com>
> wrote:
>>
>> mysql> select count(*) from metadata_text;
>> +----------+
>> | count(*) |
>> +----------+
>> | 25249913 |
>> +----------+
>> 1 row in set (3.83 sec)
>
>
>
> There are problems where a simple sequential log file is superior to a
> database table. The above looks like a log ... a very large number of
> events, without an immediate customer. For sequential access, a simple file
> is *vastly* superior to a database table.
>
> If you are thinking about indexed access to the above as a table, think
> about the cost of adding items to the index, for that many items. The cost
> of building the index is not small. Running a map/reduce on sequential files
> might be faster.
>
> Again, I do not have enough context, but ... 25 million rows?
>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to