Created
July 22, 2013 18:48
-
-
Save clr/6056452 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Casey Rosenthal | |
2:40 PM | |
k | |
what would be a good platform for ProServ to ask some questions? | |
like | |
are Links dead? can we deprecate them? | |
2i => we end up frequently recommending clients *not* use 2i, and implement a term-based inverted index instead | |
Epic Redmond | |
2:42 PM | |
I'd love to. I didn't even want to put them in the docs | |
Casey Rosenthal | |
2:42 PM | |
can we augment 2i with a term-based solution? | |
Epic Redmond | |
2:42 PM | |
well, that's a harder call. apparently many people still love 2i | |
we were just talking about that today | |
Casey Rosenthal | |
2:43 PM | |
so, maybe we don't have to kill 2i | |
but I'm finding a lot of evidence in CliServ that it causes performance probelms | |
and our testing shows that even a shitty client-side term-based index in Ruby blows the shit out of 2i in a read-heavy scenario | |
and frankly, explaining to a client that 2i has an anti-scaling pattern is embarrassing | |
Epic Redmond | |
2:45 PM | |
right, hopefully it'll just starve to death | |
Casey Rosenthal | |
2:45 PM | |
well... | |
is that the plan? | |
don't update 2i, and let it die? | |
because if so, that impacts how we conduct training | |
there was also a gist out there a while back regarding replacing m/r with something more useful | |
at this point in time, we basically have no recommended use for m/r | |
which is also mildly embarrassing to explain to a client | |
especially the ones that throw lots of $ at us | |
Epic Redmond | |
2:47 PM | |
fuck my wifi keeps flailing… are you getting any of my messages? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment