Hello Steffen, Sorry about that. I have 0.11 version intalled here really. I've just look 0.12 source code to try to understand that. There are a lot of code for fix this problem ! cache.py and threadLocal .. my bad.. :-) I would must have to try an upgrade before.
I've try to do a CacheManager but my knowlegments of python is limited. I've been trying to implement a Singleton, but it is not so simple on python. = / Whatever, that has been seem solved. I will planning to do a upgrade on test enviroment. Thanks for your attention ! Eduardo L. Fabricio. 2011/3/18 <[email protected]> > Today's Topic Summary > > Group: http://groups.google.com/group/trac-dev/topics > > - Digest for [email protected] - 2 Messages in 1 > Topic<#12ecb03b8d4e21c7_group_thread_0>[2 Updates] > > Topic: Digest for [email protected] - 2 Messages in 1 > Topic<http://groups.google.com/group/trac-dev/t/457da3b86ba8080a> > > Eduardo Fabricio <[email protected]> Mar 18 12:46PM -0300 > ^<#12ecb03b8d4e21c7_digest_top> > > Hello guys, > > Before open a ticket, i would like to talk a bit about a big problem , > that > i'm getting here. > Sorry for my pour english ok. !! Oo > > We have used the trac around 5 years. My version is not the lastest, i > use > Trac 0.12.4. > I have developed some issues and fixes on my enviroment for internal > use > only. > > The Code : > > In ticket/api.py there is this code on get_ticket_fields method : > > # Default select and radio fields > selects = [('type', model.Type), > ('status', model.Status), > ('priority', model.Priority), > ('milestone', model.Milestone), > ('component', model.Component), > ('version', model.Version), > ('severity', model.Severity), > ('resolution', model.Resolution)] > > for name, cls in selects: > > options = [val.name for val in cls.select(self.env, db=db)] > > if not options: > # Fields without possible values are treated as if they > didn't > # exist > continue > field = {'name': name, 'type': 'select', 'label': name.title(), > 'value': self.config.get('ticket', 'default_' + name), > 'options': options} > if name in ('status', 'resolution'): > field['type'] = 'radio' > field['optional'] = True > elif name in ('milestone', 'version'): > field['optional'] = True > field['standard'] = True > fields.append(field) > ...... > > > The Problem: > > We have use trac a lot and today we have exactly 428 milestones > completed. > There is a escalability problem. Because on some pages, for example: > roadmap, and ticket view or new ticket, the system uses common code to > provide ticket infos. If i got it correctly TicketSystem is the central > source of these infos ok ? > But today I need wait about 16 seconds to view the ROADMAP page and > this is > a progressive problem. > > The question is : the list of all millestones only is necessary to CRUD > ticke views. Edit, Insert , etc. > > But today, when i request the roadmap view. The trac selects all > tickets > for all milestones and for each ticket the TicketSystem selects all > milestones. > Could you help me ? Well, if you cannot help me, no problem. But i > could > alert you about it. because to enteprise use of trac, this is a > problem. > And today i believe the trac is the better system to little and middle > size > companies. I have experiment Jira system. But for me, is a Cannon to > kill > an ant. =P . Trac is a simple and effective SCM system. > > Well, thanks very much, > Best Regards, > > > Eduardo L. Fabricio > Java Developer / SCM manager. > > > > > Steffen Hoffmann <[email protected]> Mar 18 08:58PM +0100 > ^<#12ecb03b8d4e21c7_digest_top> > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > > Am 18.03.2011 16:46, wrote Eduardo Fabricio: > > Hello guys, > > > Before open a ticket, i would like to talk a bit about a big problem > , > > that i'm getting here. > > Good way to go, welcome. > > > Sorry for my pour english ok. !! Oo > > Just go on and especially don't worry about this. There is a good > number > of your kind - non-native English speakers/writers. > > > We have used the trac around 5 years. My version is not the lastest, > i > > use Trac 0.12.4. > > (Almost) Impossible. Unless you provide evidence for secret time travel > I would insist that 0.12.2 is the latest version - in our universe. May > we assume it is 0.11.4 you're talking about? :-) > > > The Problem: > > > We have use trac a lot and today we have exactly 428 milestones > > completed. There is a escalability problem. > > I recall having seen core development talking about scalability. > Roadmap > has been a part considered for improvements. But as the resources are > quite limited these days almost all efforts go into 0.13dev and > maintenance of 0.12 by building a follow-up to 0.12.2 . > > If it's feasible for you to upgrade and get involved in testing current > code it would be much more likely to find a solution for your issue, if > it's not already (partially) solved by the upgrade. > > I.e. Trac0.12 got a CacheManager for more uniform handling of often > needed content, so it might really be worth to try an upgrade. But I've > seen production data messed in untested upgrade scenarios after such a > recommendation. Certainly Trac is virtually bug-free ;-) , still I > explicitly urge you to try after a full backup, or even better: try on > a > copy of you system in a dedicated test setup. > > Others here could prove me wrong regarding fixes for your old version > or > at least give a response more precisely targeted to your request and > code. We'll see. > > Sincerely, > > Steffen Hoffmann > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk2DuW4ACgkQ31DJeiZFuHcy/ACgrMDqwhNulsEN7U2iZ3wqxZX8 > aGIAoIz94nE0MuNdXTygCMF7l1HvMEF8 > =0AFP > -----END PGP SIGNATURE----- > > > > -- > You received this message because you are subscribed to the Google Groups > "Trac Development" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/trac-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
