I saw the results of this
at
https://software.intel.com/en-us/articles/enhancing-the-scalability-of-memcached-0
Did this ever get merged into the 1.6 branch of memcached?
On Tuesday, October 16, 2012 at 10:09:13 AM UTC-7, rajiv wrote:
>
> Hi,
>
> You can find it at:
>
> https://github.com/r
Hi,
You can find it at:
https://github.com/rajiv-kapoor/memcached/tree/bagLRU
Let me know if you have any problems.
thanks,
\rajiv
On Sunday, October 7, 2012 6:05:02 PM UTC-7, 连海东 wrote:
> Hi rajiv:
>
> I didn't find the badLRU branch on 1.6 repo, where can I get your branch?
>
> Thanks
Hi rajiv:
I didn't find the badLRU branch on 1.6 repo, where can I get your branch?
Thanks
在 2012年7月2日星期一UTC+8下午11时50分42秒，rajiv写道：
>
> The bagLRU engine is now available. Please see the other post about
> this. Do let me know if you have any questions or issues.
>
> thanks,
> \rajiv
>
> On
On Wednesday, June 20, 2012 9:40:56 PM UTC-7, rajiv wrote:
>
> We would like to contribute these changes back to the 1.6 branch. Can
> someone tell me or point me to info on the process to do that? Is it is
> multi step process where I first need to upload the entire 1.6 version that
> we h
Hi Dormando,
I have pushed the bagLRU engine to a separate branch. Please see my other
post for details.
I would like to know what I need to do to get the bag LRU and the CPU
affinity changes into the regular distribution. I mean - do you need to
see interest/feedback from others in the im
The bagLRU engine is now available. Please see the other post about this.
Do let me know if you have any questions or issues.
thanks,
\rajiv
On Monday, June 25, 2012 10:46:19 PM UTC-7, Viks wrote:
> Hi,
>
> Can I get this new build for testing. I would really really want to do
> some expe
OK it worked this morning and the branch has been pushed as "bagLRU"
thanks,
\rajiv
On Thursday, June 28, 2012 8:09:54 AM UTC-7, rajiv wrote:
> > I tried:
> > git push origin bagLRU
> > but it did not do anything - just sat there forever.
>
> Actually finally it came back with a connection tim
> I tried:
> git push origin bagLRU
> but it did not do anything - just sat there forever.
Actually finally it came back with a connection timeout:
rkapoor1@RKAPOOR1-MOBL4 /c/projs/mcd/memcached (bagLRU)
$ git push origin bagLRU
error: Connection time-out while accessing
ht
> push back to your own branch
OK I have ported the changes to the latest engine-pu branch from github on
a local branch I created (called bagLRU). How do I push this back to
github??
I tried:
git push origin bagLRU
but it did not do anything - just sat there forever.
Here is the output
Sure.
I should be able to push a branch in a couple of days. Would love for
someone other than me to give it a try :)
thanks,
\rajiv
On Monday, June 25, 2012 10:46:19 PM UTC-7, Viks wrote:
> Hi,
>
> Can I get this new build for testing. I would really really want to do
> some experiment o
Hi,
Can I get this new build for testing. I would really really want to do some
experiment on this.
-vikas
On Thursday, 21 June 2012 10:10:56 UTC+5:30, rajiv wrote:
>
> Hi,
>
> I work at Intel and we have added a new optimized "engine" to Memcached
> 1.6. This engine uses parallel hash tab
oops!
I did it correctly this time but it still complained. However I changed
the name of the branch to "remotes/origin/engine-pu" and that seems to have
worked (I do see the code as expected):
==
rkapoor1@RKAPOOR1-MOBL4 /c/projs/mcd/memcac
git checkout -b rajivs_local_test_branch origin/engine-pu
that middle part is important :)
On Sun, 24 Jun 2012, rajiv wrote:
> Still shows the same code as before:
>
> ==
> $ git checkout -b origin/engine-pu
> Switched to a new branch 'origin/engine-
Still shows the same code as before:
==
$ git checkout -b origin/engine-pu
Switched to a new branch 'origin/engine-pu'
rkapoor1@RKAPOOR1-MOBL4 /c/projs/mcd/memcached (origin/engine-pu)
$ ls
AUTHORS READMEglobals.c protocol_binary
git clone etc
cd memcached
git checkout -b rajiv origin/engine-pu
On Sun, 24 Jun 2012, rajiv wrote:
> I am having some git newbe trouble with the step 2.5:
>
> "2.5: switch to engine-pu branch (after cloning)"
>
> I did the fork and clone and I got the follwing on my local machine:
>
I am having some git newbe trouble with the step 2.5:
"2.5: switch to engine-pu branch (after cloning)"
I did the fork and clone and I got the follwing on my local machine:
==
rkapoor1@RKAPOOR1-MOBL4 /c/projs/mcd/memcached (master)
$ ls
AUTHORS
That's a start, yes!
but:
2.5: switch to engine-pu branch (after cloning)
4: push back to your own branch
are all of the details.
On Thu, 21 Jun 2012, rajiv wrote:
> OK I am going to do it the right way :) Question - are these the right steps
> to do this :
>
> 1. "Fork" the repository on
OK I am going to do it the right way :) Question - are these the right
steps to do this :
1. "Fork" the repository on GitHub
2. "Clone" the repository to my local machine
3. Make my changes to the code locally
4. "Push" the commits back to gitHub
thanks,
\rajiv
On Thursday, June 21, 2012 10:
> Is there any value in posting what I have today that was written against
> 1.6.0 Beta1?
Go for it, if you want!
Life will be much easier if you can use git to check out the code tree.
Then you can compare tags, look at commit history for context, etc.
But if not, then yes you're sort of stuck with what github can offer you
as a download link.
Libevent is bundled at package time, so we don't have to keep it
I just downloaded from the engine-pu tree from
https://github.com/memcached/memcached/tree/engine-pu. The only way I
could download was as a ZIP file. I don't see any link there to download a
tarball. Not that difference is important but I notice that the contents
of the ZIP are quiet diffe
Hi Dormando,
Thanks for your detailed reponse.
> what version of 1.6 have you written this against?
We made the changes to 1.6.0 Beta1. Any idea how different is that from
engine-pu? I will grab the sources from
https://github.com/memcached/memcached/tree/engine-pu and start porting the
c
Hey,
Wow, that sounds neat! I was hoping to bum some free hardware from intel
so I could continue optimizing the 1.4 tree... :)
Any way, what version of 1.6 have you written this against? One of the
released beta's or the source tree?
https://github.com/memcached/memcached/tree/engine-pu
Our ma
nice i think dormando is the best guy to explain it to you
wait a moment dormando normally read a lot this list
2012/6/21 rajiv
> Hi,
>
> I work at Intel and we have added a new optimized "engine" to Memcached
> 1.6. This engine uses parallel hash table accesses and an LRU
> implementation that
Hi,
I work at Intel and we have added a new optimized "engine" to Memcached
1.6. This engine uses parallel hash table accesses and an LRU
implementation that gives us lock free GET operations. We have tested this
version doing GET operations on 1 to 16 cores and seems to scale pretty
well.
25 matches
Mail list logo
