[Owfs-developers] another system design question, databases and flash

2014-11-23 Thread Jerry Scharf
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

Re: [Owfs-developers] 3.3V bus master

2014-11-23 Thread Nico Bouthoorn
see my project: http://fstab.nl/beaglebone Nico Jerry Scharf wrote: Paul, I was looking at that as well. Does anyone know what other hardware/software/configuration would be needed to hang one or more of these off an I2C interface of a beaglebone black? I am already going to build a board

Re: [Owfs-developers] another system design question, databases and flash

2014-11-23 Thread Roberto Spadim
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 be

Re: [Owfs-developers] another system design question, databases and flash

2014-11-23 Thread Jan Kandziora
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

Re: [Owfs-developers] another system design question, databases and flash

2014-11-23 Thread Jerry Scharf
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

Re: [Owfs-developers] another system design question, databases and flash

2014-11-23 Thread Roberto Spadim
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