Timeline for Design review for application facing memory issues
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2011 at 2:41 | comment | added | Mr Moose | @JamesAnderson, thanks for your input. I understand your concern regarding EAV, however I have to say, in this instance, it has served us well so far. Retreiving results via pivot queries with dynamic columns is never going to be exceptionally fast, but it sure beats searching thousands of text files. I don't have much say on the machines being used unfortunately as this is deployed on multiple machines at a clients site. I do like the idea of stuffing the data into a staging table for verification first though. Thanks for the food for thought. | |
| Nov 17, 2011 at 1:57 | comment | added | James Anderson | @Mr. Moose, just didn't want to be seen recommending EAV as a general solution. Looks like its your only man. I still recommend loading the base files into tables just to get "free" indexing and buffer management to solve your memory issue. Comment on 8gb machine not being that expensive still stands though :-) | |
| Nov 16, 2011 at 14:15 | comment | added | Mr Moose | No flamewar. EAV isn't really the issue. I just thought I'd mention it as background info. We can't really use any other form of schema as the data in the reports only really has around 2 or 3 columns that you'd expect to find across all datasets. The rest of the columns can be anything else that was considered of interest. The metadata doesn't describe the columns, only some basic info of the report. Thanks for your input though. I do appreciate it. | |
| Nov 16, 2011 at 14:00 | comment | added | maple_shaft♦ | I can see this evolving into an EAV flamewar akin to Emacs vs. Vi | |
| Nov 16, 2011 at 13:16 | comment | added | Ramhound | This does not solve his problem unless his application runs as a x64 process and many applications on a x64 operating system do not. This also does not prevent extreme amounts of memory from being used. While I would admit adding a more powerful machine, based on the fact the application performance is poor is a good idea, its certainly only going to mask the problem. | |
| Nov 16, 2011 at 10:31 | comment | added | James Anderson | It may be more cost effective to buy a bigger machine. A 64 bit machine with 8 gb is not that expensive these days! | |
| Nov 16, 2011 at 10:29 | history | answered | James Anderson | CC BY-SA 3.0 |