another quesiton if you are using a database that only insert and
select (no delete/update) , you can use a more optimized database engine,
for example, you don't need to
begin
insert
commit
you can only insert, each insert is a 'automatic commit', this reduce qps,
other thing, instead of a jo
well... if you are using a time based table, something like
table(
datetime,
channel,
value,
primary (datetime,channel)
)
you can use some datetime rounding, for example
datetime = floor( microtime() / 0.5) *0.5
each 0,5 seconds you will get a new row, just an idea, there's more than
this you can
Roberto,
The problem comes from wanting to use a classic MVC web system. In these
systems, the assumption is that the database is the true state and that
the web draws whatever is in the database. Since I am scanning each of
the power supplies several times a second, this means that the databa
Am 23.11.2014 um 09:13 schrieb Jerry Scharf:
>
> I am using a flash only system to be the master of my system for testing
> 300 power supplies. I want to use a MVC database/web design. In a normal
> disk based system, I wouldn't give the fact that the state of the each
> power supplies and micr
I dom't undestood the problem
You will write how many times per second? What's the minimal period that
you need? Maybe a compact file should solve this problem
Em domingo, 23 de novembro de 2014, Jerry Scharf <
sch...@lagunawayconsulting.com> escreveu:
> Hi,
>
> I am using a flash only system to
Hi,
I am using a flash only system to be the master of my system for testing
300 power supplies. I want to use a MVC database/web design. In a normal
disk based system, I wouldn't give the fact that the state of the each
power supplies and microcontroller card is being updated several times a
