Hi Manish, This was an issue with libmemcached header files paths on Ubuntu 10.04, it is now fixed in the latest version on Github.
Yossi On Friday, July 5, 2013 8:48:59 PM UTC+3, Manish Jain wrote: > > Hi, > > Here's the required information: > 1) # lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 10.04.2 LTS > Release: 10.04 > Codename: lucid > > dpkg output and config.status are attached. > > Cheers, > Manish > > > > > On Fri, Jul 5, 2013 at 12:00 AM, Yiftach Shoolman > <[email protected]<javascript:> > > wrote: > >> Hi Manish, >> >> Looks like an issue with the libmemcached, to understand what's wrong >> please provide: >> 1. Output of 'lsb_release -a' >> 2. Output of 'dpkg -l' >> 3. The config.log file that was created by the configure script. >> >> >> On Fri, Jul 5, 2013 at 2:33 AM, Manish Jain <[email protected]<javascript:> >> > wrote: >> >>> Hi, >>> >>> When I try to run make on the code, I get this error: >>> # make >>> >>> g++ -DHAVE_CONFIG_H -I. -I/usr/local/include -O2 -g -Wall -MT >>> memtier_benchmark-protocol.o -MD -MP -MF >>> .deps/memtier_benchmark-protocol.Tpo -c -o memtier_benchmark-protocol.o >>> `test -f 'protocol.cpp' || echo './'`protocol.cpp >>> protocol.cpp:538: error: ‘protocol_binary_response_no_extras’ does not >>> name a type >>> protocol.cpp: In member function ‘virtual int >>> memcache_binary_protocol::write_command_set(const char*, int, const char*, >>> int, int)’: >>> protocol.cpp:570: error: ‘protocol_binary_request_set’ was not declared >>> in this scope >>> protocol.cpp:570: error: expected ‘;’ before ‘req’ >>> protocol.cpp:572: error: ‘req’ was not declared in this scope >>> protocol.cpp:573: error: ‘PROTOCOL_BINARY_REQ’ was not declared in this >>> scope >>> protocol.cpp:574: error: ‘PROTOCOL_BINARY_CMD_SET’ was not declared in >>> this scope >>> protocol.cpp:576: error: ‘PROTOCOL_BINARY_RAW_BYTES’ was not declared in >>> this scope >>> protocol.cpp: In member function ‘virtual int >>> memcache_binary_protocol::write_command_get(const char*, int)’: >>> protocol.cpp:593: error: ‘protocol_binary_request_get’ was not declared >>> in this scope >>> protocol.cpp:593: error: expected ‘;’ before ‘req’ >>> protocol.cpp:595: error: ‘req’ was not declared in this scope >>> protocol.cpp:596: error: ‘PROTOCOL_BINARY_REQ’ was not declared in this >>> scope >>> protocol.cpp:597: error: ‘PROTOCOL_BINARY_CMD_GET’ was not declared in >>> this scope >>> protocol.cpp:599: error: ‘PROTOCOL_BINARY_RAW_BYTES’ was not declared in >>> this scope >>> protocol.cpp: In member function ‘const char* >>> memcache_binary_protocol::status_text()’: >>> protocol.cpp:636: error: ‘m_response_hdr’ was not declared in this scope >>> protocol.cpp:636: error: ‘PROTOCOL_BINARY_RESPONSE_SUCCESS’ was not >>> declared in this scope >>> protocol.cpp: In member function ‘virtual int >>> memcache_binary_protocol::parse_response(bool)’: >>> protocol.cpp:651: error: ‘m_response_hdr’ was not declared in this scope >>> protocol.cpp:654: error: ‘m_response_hdr’ was not declared in this scope >>> protocol.cpp:657: error: ‘PROTOCOL_BINARY_RES’ was not declared in this >>> scope >>> protocol.cpp:700: error: ‘PROTOCOL_BINARY_RESPONSE_SUCCESS’ was not >>> declared in this scope >>> ---- >>> >>> # g++ --version >>> g++ (Ubuntu 4.4.3-4ubuntu5) 4.4.3 >>> >>> Any ideas why? >>> -Manish >>> >>> >>> >>> On Tue, Jul 2, 2013 at 3:10 PM, Yiftach Shoolman >>> <[email protected]<javascript:> >>> > wrote: >>> >>>> We have just released our memtier_benchmark tool for testing Redis >>>> under heavy load: >>>> >>>> 1. >>>> Here<http://garantiadata.com/blog/memtier_benchmark-a-high-throughput-benchmarking-tool-for-redis-memcached#.UdNZlD5gaRI> >>>> is >>>> a short blog post that describes its capabilities >>>> 2. And here <https://github.com/GarantiaData/memtier_benchmark> is >>>> the GitHub repository >>>> >>>> In a nutshell: >>>> >>>> 1. It is capable of launching multiple worker threads , with each >>>> thread driving a configurable number of clients >>>> 2. You can control the ratio between GET and SET operations >>>> 3. The tool offers control over the pattern of keys used by the GET >>>> and SET operations Each operation’s pattern can be set independently >>>> to be >>>> random or sequential >>>> 4. Keys’ expiry can be common or randomly set from a configurable >>>> range >>>> 5. Bonus - it can be either used for benchmarking Redis >>>> >>>> Have fun. >>>> >>>> -- >>>> >>>> Yiftach Shoolman >>>> +972-54-7634621 >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "memcached" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected] <javascript:>. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "memcached" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> >> -- >> >> Yiftach Shoolman >> +972-54-7634621 >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "memcached" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
