All,
Just FYI, I've noticed a big drop in server responsiveness since the new tools were installed (updated bugzilla, etc.) Not of immediate concern, but I wonder if new features (like bugzilla automatically searching for all related bugs, etc.) may be putting a big strain on the server. I don't know who looks at this, or if there are any stats available, but it is something to keep an eye on in the future.
It's working fine, just slow, so there is no immediate need for a fix, but if anybody has access to the box, it would be worth a check to see what the load is and where there is anything in the logs that points to a problem.
All,
Just FYI, I've noticed a big drop in server responsiveness since the new tools were installed (updated bugzilla, etc.) Not of immediate concern, but I wonder if new features (like bugzilla automatically searching for all related bugs, etc.) may be putting a big strain on the server. I don't know who looks at this, or if there are any stats available, but it is something to keep an eye on in the future.
It's working fine, just slow, so there is no immediate need for a fix, but if anybody has access to the box, it would be worth a check to see what the load is and where there is anything in the logs that points to a problem.
-- David C. Rankin, J.D.,P.E.
The load is primarily coming from the FOSWiki instance during routine search engine crawls. If we can migrate FOSWiki to MediaWiki the server will be far more responsive.
In the meantime I will see what I can do to throw additional hardware at the Web server in an attempt to mitigate this.
Tim
On 02/28/2014 11:35 PM, Timothy Pearson wrote:
The load is primarily coming from the FOSWiki instance during routine search engine crawls. If we can migrate FOSWiki to MediaWiki the server will be far more responsive.
In the meantime I will see what I can do to throw additional hardware at the Web server in an attempt to mitigate this.
Tim
Thank Tim,
I'd just wait for the Mediawiki migration. No need to mess with what's working if we have a planned migration coming. Unless you just want to throw more hardware at it :)
On 02/28/2014 11:35 PM, Timothy Pearson wrote:
The load is primarily coming from the FOSWiki instance during routine search engine crawls. If we can migrate FOSWiki to MediaWiki the server will be far more responsive.
In the meantime I will see what I can do to throw additional hardware at the Web server in an attempt to mitigate this.
Tim
Thank Tim,
I'd just wait for the Mediawiki migration. No need to mess with what's working if we have a planned migration coming. Unless you just want to throw more hardware at it :)
-- David C. Rankin, J.D.,P.E.
How did you want to handle the migration? Should I throw a MediaWiki instance up and give you full access, then let you start working?
Tim
On 03/01/2014 04:39 PM, Timothy Pearson wrote:
On 02/28/2014 11:35 PM, Timothy Pearson wrote:
The load is primarily coming from the FOSWiki instance during routine search engine crawls. If we can migrate FOSWiki to MediaWiki the server will be far more responsive.
In the meantime I will see what I can do to throw additional hardware at the Web server in an attempt to mitigate this.
Tim
Thank Tim,
I'd just wait for the Mediawiki migration. No need to mess with what's working if we have a planned migration coming. Unless you just want to throw more hardware at it :)
-- David C. Rankin, J.D.,P.E.
How did you want to handle the migration? Should I throw a MediaWiki instance up and give you full access, then let you start working?
Tim
Yes,
Give myself and E. Liddel full access. As mentioned before, I have already collected all of the templates to upload as soon as it is up and running. I think the process will go very quickly. What would really help the transition (at least from your standpoint) is a quick list of what you want to see up first:
Main Page ... ... ...
E. has apparently already began the wiki layout. We will need to get with him to see what he has and then between he and I we can do a 'divide and conquer' moving content over.
This is a good thing ;-)
On 03/01/2014 04:39 PM, Timothy Pearson wrote:
On 02/28/2014 11:35 PM, Timothy Pearson wrote:
The load is primarily coming from the FOSWiki instance during routine search engine crawls. If we can migrate FOSWiki to MediaWiki the server will be far more responsive.
In the meantime I will see what I can do to throw additional hardware at the Web server in an attempt to mitigate this.
Tim
Thank Tim,
I'd just wait for the Mediawiki migration. No need to mess with what's working if we have a planned migration coming. Unless you just want to throw more hardware at it :)
-- David C. Rankin, J.D.,P.E.
How did you want to handle the migration? Should I throw a MediaWiki instance up and give you full access, then let you start working?
Tim
Yes,
Give myself and E. Liddel full access. As mentioned before, I have already collected all of the templates to upload as soon as it is up and running. I think the process will go very quickly. What would really help the transition (at least from your standpoint) is a quick list of what you want to see up first:
The entire contents of the Developers web (http://www.trinitydesktop.org/wiki/bin/view/Developers/WebHome) The entire contents of the Documentation web http://www.trinitydesktop.org/wiki/bin/view/Documentation/WebHome
Lesser priority (can be migrated after MediaWiki goes live: Artwork Community ULab (I can handle this one)
If possible I'd like to retain the structure inherent in the FOSWiki "Webs" (a.k.a. categories). Is this something that can be done with MediaWiki?
E. has apparently already began the wiki layout. We will need to get with him to see what he has and then between he and I we can do a 'divide and conquer' moving content over.
This is a good thing ;-)
Yes it is. :-)
Out of curiosity, how is the Web server responding now? I have implemented some changes and it seems to be responding OK in my limited testing thus far (but FOSWiki will still slow it down).
Thanks!
Tim
On 03/01/2014 08:40 PM, Timothy Pearson wrote:
Yes,
Give myself and E. Liddel full access. As mentioned before, I have already collected all of the templates to upload as soon as it is up and running. I think the process will go very quickly. What would really help the transition (at least from your standpoint) is a quick list of what you want to see up first:
The entire contents of the Developers web (http://www.trinitydesktop.org/wiki/bin/view/Developers/WebHome) The entire contents of the Documentation web http://www.trinitydesktop.org/wiki/bin/view/Documentation/WebHome
Lesser priority (can be migrated after MediaWiki goes live: Artwork Community ULab (I can handle this one)
If possible I'd like to retain the structure inherent in the FOSWiki "Webs" (a.k.a. categories). Is this something that can be done with MediaWiki?
Yes. Mediawiki uses namespaces for logical groupings. I'll see how the FOSWiki categories are done and mirror that in mediawiki.
E. has apparently already began the wiki layout. We will need to get with him to see what he has and then between he and I we can do a 'divide and conquer' moving content over.
This is a good thing ;-)
Yes it is. :-)
Out of curiosity, how is the Web server responding now? I have implemented some changes and it seems to be responding OK in my limited testing thus far (but FOSWiki will still slow it down).
Thanks!
Tim
Well "Offline for maintenance" appeared faster than usual :)
-
David C. Rankin -
Timothy Pearson