On Thu, 2005-11-24 at 13:18 +0000, JUAN ERNESTO FLORES BELTRAN wrote:
carlos wrote:
You still haven't said what sampling speed you need, but unless it is slow, you will need to save somewhere else first (as fast as posible), and then move to the database as a post process.
Sampling speed will be as slow as possible because of this is a project for the university...not a product for anyone so speed is subject to the designer programming skills and available resources: adquisition data card specifications, programming language, etc...
just to get an idea...what limit is considered "too fast" to save somewhere else before saving into the database?? and what technical reasons would
Depends on the acquisition card. Some intelligently buffer data so an OS can take it when it can. Some only return a current value. So, the requirements of the OS are determined first by the card and secondly by how well the device driver is written. Are you wanting 200 values a second? 32000? 1000000?
force me to do this in case sampling speed increases where neccesary?? is this subject to any mysql or postgresql managing/storaging data limitations??
I doubt you would make the database direct. With some planning, you could, for example, make an acquisition program that writes to a flat disk file (for speed), and another program that reads this file and puts it in a database. They could run at the same time. -- Roger Oberholtzer OPQ Systems AB