If the issue is fixed, I vote we leave things as-is (if it ain't broke, don't fix it).
Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Mon, Feb 13, 2012 at 10:47 AM, Oskar Berggren <[email protected]>wrote: > I asked Atlassian what integrations would be disabled. However, before > I got a reply on that they also found and fixed the true issue. I'm > now seeing typical response times of about 0.5 seconds to load an > issue - down from 5-10 seconds before. Oh boy, this is nice! > > The issue had to do with the github connector: > https://studio.atlassian.com/browse/BBC-135 > > > At this point I'm not aware of any reason to proceed with a migration > to JIRA only, but for completeness, here is the list of what would be > lost: > > Quote: > No FishEye (Source tab) integration > No Crucible (Reviews tab) integration > No Confluence (Wiki tab) integration > No Bamboo (Builds tab) integration > No Subversion > > github and BitBucket integration will still continue to work. In any > case, please let us know how you wish to proceed. > EndQuote. > > > If no one speaks up with different ideas within a day or two, I will > tell Atlassian that we are happy with the fix and to NOT proceed with > a migration. > > /Oskar > > > > 2012/2/10 Stephen Bohlen <[email protected]>: > > If that turns out to be it, then I concur that we can almost certainly > > safely accept their suggestion. > > > > > > Steve Bohlen > > [email protected] > > http://blog.unhandled-exceptions.com > > http://twitter.com/sbohlen > > > > > > On Fri, Feb 10, 2012 at 7:56 AM, Oskar Berggren < > [email protected]> > > wrote: > >> > >> I interpreted it as anything other than SCC integration, but it seems > >> prudent to check. I will do so. > >> > >> /Oskar > >> > >> > >> 2012/2/10 Stephen Bohlen <[email protected]>: > >> > Can we check to see if they really mean "integration with various SCC > >> > systems" (like bitbucket, git, etc.) or do they mean "integration with > >> > other > >> > Atlassian products" (like Bamboo, Fisheye, Greenhopper, etc. that are > >> > part > >> > of the rest of their OnDemand product suite)? Its not clear to me > what > >> > they > >> > mean in their reply. > >> > > >> > My initial reading was sim. to yours (e.g., it was referring to > github. > >> > bitbucket, etc. integration) but their references to our not using > other > >> > "OnDemand" subsystems makes me think that they might actually not be > >> > referring to SCC integration per se. Can we check/clarify w/ them > >> > exactly > >> > what they are proposing to "shut off" --? > >> > > >> > Steve Bohlen > >> > [email protected] > >> > http://blog.unhandled-exceptions.com > >> > http://twitter.com/sbohlen > >> > > >> > > >> > > >> > On Fri, Feb 10, 2012 at 5:44 AM, Roger Kratz < > [email protected]> > >> > wrote: > >> >> > >> >> << ... which is the github integration as far as I can tell>> > >> >> << They now propose to migrate to a Jira-only model, since we don't > >> >> actually use any of the integrations available in Jira Studio. Is it > >> >> true > >> >> that we don't use any of the integrations?>> > >> >> > >> >> No, it's not true - it is used in NHibernate.Envers project. At least > >> >> if I > >> >> understand "integration" in this context correctly? Envers (on > >> >> BitBucket) > >> >> changesets and its source code are "integrated" with Jira issues > based > >> >> on > >> >> the commit message. > >> >> > >> >> It's a nice feature but if it kills performance it's a no-brainer... > >> >> Can > >> >> live without it. > >> >> > >> >> /Roger > >> >> > >> >> -----Original Message----- > >> >> From: [email protected] > >> >> [mailto:[email protected]] On Behalf Of Oskar > >> >> Berggren > >> >> Sent: den 10 februari 2012 11:21 > >> >> To: [email protected] > >> >> Subject: [nhibernate-development] Jira performance continued - remove > >> >> integrations? > >> >> > >> >> Hi, > >> >> > >> >> To followup on the previous thread about Jira performance. As I've > >> >> mentioned before I have an open support request with Atlassian, which > >> >> have > >> >> now been escalated to a developer. > >> >> > >> >> They had a suspicion that we were suffering from a variation of > >> >> https://studio.atlassian.com/browse/GHC-105 (GHC causes extreme > >> >> performance degradation) which is the github integration as far as I > >> >> can > >> >> tell. > >> >> > >> >> They now propose to migrate to a Jira-only model, since we don't > >> >> actually > >> >> use any of the integrations available in Jira Studio. Is it true that > >> >> we > >> >> don't use any of the integrations? How do you feel about this > proposal? > >> >> Full > >> >> text from Atlassian below: > >> >> > >> >> A comment from their developer: > >> >> > >> >> "Very sad to hear that your instance is experience poor > performance, > >> >> indeed our > >> >> new platform is expected to deliver an massive improvement on > >> >> response > >> >> times > >> >> and stability for large instances as this one, unfortunately > looks > >> >> like we may have > >> >> been hitting a bug/contention on the software side, as the > machine > >> >> load is very > >> >> low. I'm digging further to try to understand where the > contention > >> >> is > >> >> happening. > >> >> > >> >> I agree with you that 10+ seconds to view a page is unacceptable > >> >> and I > >> >> can > >> >> guarantee that this is not the average response time we try to > >> >> deliver > >> >> on the > >> >> OnDemand platform." > >> >> > >> >> > >> >> And the proposal: > >> >> > >> >> "I noticed that you guys have a full OnDemand license but have > >> >> disabled > >> >> all the > >> >> other applications tabs, leaving just JIRA, looking on the other > >> >> apps > >> >> doesn't seem > >> >> to anyone using them, in that case I would suggest that we > migrate > >> >> your license > >> >> to be JIRA only, that will remove a lot of OnDemand integrations > >> >> with > >> >> the other > >> >> apps that no-one is using, that will most certainly increase the > >> >> performance. > >> >> > >> >> Please let me know if JIRA is the only application you need on > this > >> >> instance so > >> >> we can make the switch, and after we do that we can monitor to > see > >> >> if > >> >> it still > >> >> shows slow response times." > >> >> > >> >> > >> >> > >> >> /Oskar > >> > > >> > > > > > >
