Hello All,

Well, this week has been a decent week in that not too many pressing things were slammed onto my plate which was great!

Still, did some bug fixes and am in the middle of a project with Andrew_ to speed up those personal pages!

Bug Fixes:

1. Posts on WC would duplicate the linetext of the articles! Bad bug! This was fixed by updating one of our stored procedures
2. Some Posts were being saved with blank lines within the articles DB
3. If a skin author who owns a personal page creates his first skin within a particular skin category and the skin goes into moderation and/or processing, that skin is no where to be found within his personal page. This has been fixed.
4. Within the Gallery Section of each personal page, there exists a drop down list and if that author has skins in moderation, there should is an item of the drop down list that says “In Moderation” that you can select to see skins that have not yet been approved. Well, Skins’ status can also be “In Processing”, so I added that entry within that drop down list so you can also see skins that are in processing
5. In the MySkins.aspx page, if a skin author doesn’t have any approved skins, but has skins in moderation or in processing, there was no way to view these skins. This bug has been fixed.

MISC Things worked on this week.
1. Andrew_ and I have tag teamed on making the personal pages faster. First let me say I love when things work smoothly between co-workers. By Splitting the duties, this little project will get done a bit faster, but most importantly, it will be done in a way that is much more expandable because there is twice the man power to implement the correct system!
The duties were split as follows:
a. Andrew_ is in charge of all the usercontrols we want to make static. He has created a system such that they will inherit from this nice little class and will create static files from these controls to save from db activity as well as server side processing. That system, in tandem with implementing them with all the controls is a tall task, and he basically finished it by wed which was awesome.
b. What I’m in charge with is setting up the proper tables within the DB and also some internal things that interact with his system such that if a control needs to refresh itself, the system I created will send a message to his control, and the control will refresh itself.

The system should be done by Monday or Tuesday and the team will Test and debug it, and hopefully the system will be in place live by wed or thurs.
I’ve learned a few things from this project that I can carry over to my next project which is implementing moderators for our forums. Once this project is done with, that is the next beast to tackle! Oh fun it will be let me tell you!

Well, have a great weekend all!!

Flyin

Hello all,

This week was one that I desparately needed. Our sites have been it's most stable this week since our move to chicago.
Still things to do to help with that, but that will be discussed later

Bugs Fixed:
1. Cannot Edit or delete posts
2. Editing and/or setting article's status is too slow
3. Within the libraries, the "Top Authors" Section of the right bar wasn't showing correctly.
4. Page Count for article comments was displaying incorrectly. For Example, if there are 4 pages of article replies, it was only showing as having 3, you would actually have to manually type in the url the 4th page.
5. Users could not move his/her posts from one forum to another in certain cases.

These are all bugs i had a chance to get to this week and now are currently SQUISHED!

MISC things done to help with site/server performance:
1. Did some profiling of our sites as usual, and just made sure our key queries weren't taken longer than usual, and noted others that need some TLC
2. Created some stored procedures to help with syncing articles from one db to another so that the process would be much more zippy when editing/deleting/setting status of articles.
3. When creating/editing/deleting an article from your blogsite of JU, it now queue's a job to sync that particular to our articles DB.
4. This task took most of the time this week, but i feel will help us in the long run.
Late last week, one of our external developers who is a whiz at Databases made a suggestion on how to structure a few of our intense queries. Well, Here are a few "things" that his suggestion has made an impact with:
a. Article Comments. Our methods of retrieving article comments wasn't bad, but was very average. this change made a 300% improvement in speed and efficiency.
b. Skin Comments. Similiar to the skin comments, it has made a significant impact in change.
c. Viewing and paging through featured articles
In all, i updated roughly 21 stored procedures to benefit from Alberto's suggestion. I figure i mine as well do it now before it becomes a major issue.

Some Key things that need to be addressed next week:
1. When a skin is created or approved, it doesn't always show up properly throughout the WC Main site as well as that author's personal page.
2. Personal pages!!!! Three key words - "Faster" "Faster" "Faster
we will be concentrating alot on using the new static page system t-man created this week and implementing it within the personal pages so that the browsing experience is much much better.

Well, i'm sure i forgot a few items, but that is it for the week. Have a great weekend! the weather in detroit is beautiful!

Flyin

It's been a short week, but have made a few big strides!

Optimization was the name of the game this week.

As you guys and gals know, our sites haven't been as happy as we all would like them to be lately which is due in part to alot of things, but which has raised

a very very large red flag.

Now on to the Updates:

1. We learned a little bit ago, for all you .net web developers out there, that when you use an SQLDataReader that it does not get closed naturally after it is done doing a databind rather it holds the connection to the database open until the garbage collector comes by and does the proper actions for the datareader.  Well, This fix took me a while!  I went through all of our Wincustomize based code, which as you can imagine is large and made sure that all instances of SQLDataReader are opneing and closing the datareaders in a proper fashion with the proper exception handling to wrap around each code block.
2. One of our developers emailed T-man and I today with something he has seen us do alot of which apperently isn't the most effective way to page through mounds and mounds of records.  Take for instance our Marathon thread, for quite some time now the thread has been unreadable and unmanageable on our part because the query to populate that bad boy has just been flat out painful.  Well, with the suggestions by Alberto, we have cut that query down to be over 6 times faster now than before, and although still not as fast as you guys want, it does the job much more efficiently and most of all doesn't take as much server processing to complete!
3. Our database that is currently serving up articles was very dependant on our huge master DB for information, so, if the master DB was slow in responding, articles would also be slow to respond obviously.  Well, we thought it over, and the articles DB should be independant of the master database in such a way that if the master were to go down, the community should be able to still browse articles in most circumstances, well, we have made a large stride in doing so which didn't take much time at all.  Basically, T-man setup replication on a few tables from the master DB to be copied over to the Articles DB so if need be, it can run the forum lists independently.  All i had to do on my part was change some queries so that it would no longer look at the master for some information, but would look locally within it's own DB and now things seem to respond much better.  We will see just how well.
4. I assisted Andrew_ in the forums he is writing that will soon be up for public use.  I wrote some cache callbacks for him so that when a forum listing expires from cache, it will refresh itself so that the next user will get a "faster" copy of the data and not have to wait for a call to the database.  I also did cache callbacks for the subtopic dropdownlists, and the forum bookmarks.
5. BUG: User was able to obtain the "Admin" Honorific!  Little rascal, well, i make a check to see when you change your honorific, the code checks to see if you have the proper access and if so, gives you the honorific, else, STOP HACKING THE SITE!   

Yes, if you can see i had my DBA hat on this week, well for the last few weeks profiling and such to see what is bringing down our sites.  This weekend will tell alot about the strides we have made this week.  Let's just now cross our fingers and hope for a solid weekend of sites running the way they were first intended to!

Have a great weekend all, and i don't have any good jokes, but APRIL FOOLS ANYWAYS!   

Peace out

Flyin