If any of this is ticking boxes for you, it’s time to consider what flash could do for the performance of your database:Comments Off on When You Should Consider Flash for Database Storage | Filed in Oracle | Tags: flash, storage
- I/O wait times are high. Essentially we are looking for high latency from the existing storage system. Flash memory systems should deliver I/O with sub-millisecond latency, so if you see an average latency of 8ms on random reads (db file sequential read), for example, you know there is potential for reducing latency to an eighth of its previous average value.
- I/O forms a significant percentage of Database Time. If I/O is only responsible for 5% of database time, no amount of lightening-fast flash is going to give you a big performance boost… your problems are elsewhere. On the other hand, if I/O is comprising a large portion of database time, you have lots of room for improvement.
I had a problem with a flash CFFORM. It would not show up in Internet Explorer. However, Firefox had no problem displaying it. The flash form was part of an application using the Mach-II framework (which I’m converting now to Model-Glue). I had a general layout template in which I included the body of the main page. My layout template was like this (simplified here for demonstration purposes): Continue reading…2 Comments | Filed in ColdFusion, Tips | Tags: cfform, flash, gotcha