#MusicPlaylist 1: Getting a Good Night's Sleep
I usually don't play music when I want to sleep 'cause sometimes I sing along with it.
I have to tell you this
Cause my heart goes wild
-Russian Red
Optimizing Near-real Time Module
Super-Related Post: GEODJANGO + GEOSERVER + OPENLAYERS COMBO! The scenario is we have a python script that runs on a given interval that automatically loads shapefile into PostgreSQL with PostGIS database.This shapefile is from a simulation done by a computer and it is updated on a timely basis. Near-real Time module of the app performs INTERSECT query to generate statistics. This involves two tables on the database. Every query took more than 5 minutes which is unacceptable. No matter how I try to change(optimize) my query, it's still SLOOOOOOOOOOOOOOOOOOOOOOW! So, instead of directly performing INTERSECT query between two tables every time the user take request. I have this instead: I created a stats table where the results are inserted and stored on it. After loading the shapefile into the database, a PostgreSQl function will be called and perform the INTERSECT query then insert the new result to the stats table. The database server will just perform select quer...
Comments
Post a Comment
Feel free to ask, suggest and comment regarding this post/blog. You can also contact me through e-mail, just always use the contact page. Thank you for visiting this blog.