Good progress today, did my first trial run through of the DB integrated application with good results. 3 minutes and 52 seconds to fetch, store, process and create 135 NZBs. Right now the group is static however given the progress so far the next step will be to grab a list of groups from the database.
From then, there are different paths that consider. The forefront is;
1. Setting up the backlog vs current processestems
2. Setting up threaded processing of each of the different phases (right now im thinking [NNTP, Disk2DB processing, DB2REL processing, REL2File processing])
3. DB structure for release (Date, Full subject, Size)
4. Basic front end
5. Search systems (maybe sphynx)
6. Master thread
7. Set up basic working table, status codes etc
8. Modify groups table to reflect backlog and current headers.
So there are quite a few different tasks to tackle, so I need prioritize the work. I think that it will be 3, 8, 7, 2, 6, 4, then the rest.
I did a performance profile after reading a good article (ill link it later) that talked about the harzards of trying to keep analyzing performance as you’re writing your application. I need to be careful of this so I don’t keep going back and looking at performance. The biggest hit on performance right now is oddly doing the date conversion between datetime to double. This is odd and I will need to figure out exactly what is this is doing in part of this conversion to see if there is anything I can do to take care of that performance hit.