qPU
>
> You may want to check your subscription to the pycassa mailing list; it
> seems like you're not getting my responses for some reason.
>
>
> On Tue, Feb 5, 2013 at 12:20 PM, Pradeep Kumar Mantha <
> pradeep...@gmail.com> wrote:
>
>> Hi,
>>
>&
Hi,
I am trying to read fields using pycassa api. But seems like I am missing
something and not getting expected results.
>>> pool = pycassa.ConnectionPool('usertable', server_list=['1.1.1.1'])
>>> cf = pycassa.ColumnFamily(pool, 'data')
>>> cf.get('7573657232323132333035343936323937363138343433'
python.
>
>
> I'd also closely compare the IO going on in both versions (the .write
> calls). For example this may be significantly faster:
>
> et=time_fn()
> f.write(str(colfam.get(key))+"\nTime taken for a single query is "
> + str(round(1000*(et-st),
g the pycassa performance. Please
have a look at the simple python script attached and let me know
your suggestions.
thanks
pradeep
On Thu, Jan 31, 2013 at 4:53 PM, Pradeep Kumar Mantha
wrote:
>
>
> On Thu, Jan 31, 2013 at 4:49 PM, Pradeep Kumar Mantha <
> pradeep...@gmail.com> wrot
PM, Tyler Hobbs wrote:
> Can you provide the python script that you're using?
>
> (I'm moving this thread to the pycassa mailing list (
> pycassa-disc...@googlegroups.com), which is a better place for this
> discussion.)
>
>
> On Thu, Jan 31, 2013 at 6:25 PM
nds is very suspicious. I can't
> debug your script over the mailing list, but do some sanity checks to make
> sure there's not a bottleneck somewhere you don't expect.
>
>
> On Fri, Jan 18, 2013 at 12:44 PM, Pradeep Kumar Mantha
> wrote:
>>
>> Hi,
>>
tionPool size to handle the number of
> threads you have using it concurrently. Set the pool_size kwarg to at least
> the number of threads you're using.
>
>
> On Thu, Jan 17, 2013 at 6:46 PM, Pradeep Kumar Mantha
> wrote:
>>
>> Thanks Tyler.
>>
>> I ju
etwork latency, you'll top out on python performance with
> a fairly low number of threads due to the GIL. It's best to use multiple
> processes if you really want to benchmark something.
>
>
> On Thu, Jan 17, 2013 at 6:05 PM, Pradeep Kumar Mantha
> wrote:
>>
&g
adge for that.
>
> You should use the built in stress tool or YCSB.
>
> The CLI has to do much more string conversion then a normal client would and
> it is not built for performance. You will definitely get better numbers
> through other means.
>
> On Thu, Jan 17, 2013 at
Hi,
I am trying to maximize execution of the number of read queries/second.
Here is my cluster configuration.
Replication - Default
12 Data Nodes.
16 Client Nodes - used for querying.
Each client node executes 32 threads - each thread executes 76896 read
queries using cassandra-cli tool.
Hi,
The directory information should contain entire path to the sstables location.
'C:\Anand\Workspace\H2C_POC\Customer\.
I assume customer is the keyspace.
Hope it helps.
thanks
pradeep
On Thu, Dec 20, 2012 at 6:15 AM, wrote:
> Hi
>
>
>
> I am working on options to load my sstables to loa
ion for the sstableloader ? Background
> configuration section here http://www.datastax.com/dev/blog/bulk-loading
>
>
> Hope that helps.
>
> -
> Aaron Morton
> Freelance Cassandra Developer
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.com
>
Hi!
I am trying to load sstables generated onto a running multi-node
Cassandra cluster. But I see problems only with multi-cluster and
single node works fine.
Cassandra version used is 1.1.2 .
The cassandra cluster seems to be active.
-bash-3.2$ nodetool -host 129.56.57.45 -p 7199 ring
Address
13 matches
Mail list logo
