I looked at selinium recently - looks useful. I think Marcus used it when he was working on the performance tests.
On Mon, Jul 19, 2010 at 8:43 AM, Ethan Jewett <[email protected]> wrote: > I need to investigate further and test more. I think the first baby > step is a jira ticket for automated performance tests. It's on my list > for this afternoon, after any release 1.1 stuff I can help with. > > Ethan > > On Monday, July 19, 2010, Richard Hirsch <[email protected]> wrote: >> On Sun, Jul 18, 2010 at 11:59 PM, Ethan Jewett <[email protected]> wrote: >>> The moon is pretty ominous looking in Hamburg tonight, which means >>> that it's time for "contrary Ethan" to come out of hiding. >>> >>> Actually, I agree on the UI thing, though I would like to get >>> everything on to the main page somehow, but that can come later. >>> >>> Really all I want to do is get anyone who might implement this to >>> think twice about using tracking to do this. In fact, we probably need >>> to take a really hard look at the tracking approach in general. Unless >>> I'm mistaken, every message created is distributed to every user actor >>> in the system to check if it matches a tracker for that user. >> >> In our performance tests, we never got that far. If you are correct, >> however, we will definitely have to change the track implementation. >> >>> >>> Can anyone else verify that? If this is how it's really set up, then >>> it's going to become a major problem in systems with large numbers of >>> users and I'll need to open a Jira item for it and we'll figure out >>> what to do. I'm not sure how to do it better right now, but if that's >>> how it works then it's an issue. >>> >>> That's what I'm seeing. If I'm wrong, that would be great. >>> >>> With regards to hashtag following, I think the right way to do this is >>> to set up another actor like a User actor or (to be created) >>> Conversation actor and when someone follows a hashtag the actor will >>> put the message on that user's timeline. >>> >>> Note that these conversation and hashtag actors only need to be >>> started up when someone follows a conversation or hashtag, and there >>> would be only one actor object per conversation/hashtag as opposed to >>> one per user following (as in the case of tracking). This approach is >>> also pretty efficient because we can look at a message and know >>> exactly which conversation or hashtag actor we need to forward it to >>> without querying 1000s of actors to see if they are interested in it. >>> >>> Ethan >>> >>> On Sun, Jul 18, 2010 at 10:25 PM, Anne Kathrine Petterøe >>> <[email protected]> wrote: >>>> >>>> On 18. juli 2010, at 18.55, Richard Hirsch wrote: >>>> >>>>> Thanks >>>>> >>>>> The easiest way to follow a tag from the UI would be to have a follow >>>>> button like you have on users page. It might be implemented internally >>>>> as a track. >>>> >>>> That was my thinking too. Easiest way of implementing it. >>>> >>>>> >>>>> On Sun, Jul 18, 2010 at 5:48 PM, Ethan Jewett <[email protected]> wrote: >>>>>> I added it earlier today :-) >>>>>> >>>>>> I agree that hashtag-follow would also be useful. I'll create a jira >>>>>> issue for that as well this evening or tomorrow. >>>>>> >>>>>> Ethan >>>>>> >>>>>> On Sunday, July 18, 2010, Anne Kathrine Petterøe <[email protected]> >>>>>> wrote: >>>>>>> I agree. >>>>>>> I think we should add it as Jira task to our backlog. >>>>>>> >>>>>>> Follow a hashtag would also be useful. >>>>>>> >>>>>>> /Anne >>>>>>> >>>>>>> On 17. juli 2010, at 14.01, Ethan Jewett wrote: >>>>>>> >>>>>>>> *I think this link below is a description of a very powerful new >>>>>>>> feature >>>>>>>> (following conversations and/or conversations as first-class objects) >>>>>>>> that >>>>>>>> we are well-positioned to implement. Thoughts? >>>>>>>> * >>>>>>>> >>>>>>>> * >>>>>>>> * >>>>>>>> >>>>>>>> *Enterprise microblogging needs a facelift to rival email* >>>>>>>> >>>>>>>> http://libraryclips.blogsome.com/2010/07/16/enterprise-microblogging-needs-a-facelift-to-rival-email/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+LibraryClips+%28Library+clips%29 >>>>>>>> >>>>>>>> (via Instapaper <http://www.instapaper.com/>) >>>>>>> >>>>>>> >>>>>> >>>> >>>> >>> >> >
