Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

2ari a few quick questions to you with regards to

Can I take this chance to ask what you would be looking for in a benchmark?

What would be that benchmark like? What kind of information it would provide? when would it be available?

Hi Ari, thanks for your answers.

I would like to measure the time which it takes to write/read 1M key/value pairs (assume that would be a HashMap<String, Long>) and also the time it takes to write/read hashmap with a few keys but with huge values something like 100 keys with 100K values each (data structure for that purpose HashMap<String, ArrayList<Long>>)

Unfortunately I have to make a decision by the end of the week, so sorry to say I can not wait for one month

Thanks Steve, I'll read through and try out examinator performance tests!

I was looking for some performance tests on the web-site but could not find, perhaps I was looking in the wrong place. Could anyone point me to some sort of benchmark tests or benchmark tools which I could possibly execute myself to understand how fast is terracotta on my hardware?

Thank you Ari, this answers my question!

I'm wondering if terracotta cache solution supports async persistence of in-memory data. As far as I could understand the persistence functionality is supported by Terracotta Server Arrays, but i could not find the information if its made asynchronous or not

I've got one TC server and one client application successfully up and running but when I try to start second application I've got the following output in my Administrator console

2008-07-28 09:08:30,795 [TCWorkerComm # 3] INFO com.tc.net.protocol.transport.ServerMessageTransport - ConnectionID(3.374df08f07f84afba4bf1182a72ce915): Attaching new connection: com.tc.net.core.TCConnectionJDK14@28465402: connected: true, closed: false local=10.152.113.128:9510 remote=10.152.113.128:39521 connect=[Mon Jul 28 09:08:30 EDT 2008] idle=2ms [28 read, 0 write]
2008-07-28 09:08:30,799 [TCWorkerComm # 3] INFO com.tc.net.protocol.transport.ConnectionHealthCheckerImpl. DSO Server - Health monitoring agent started for domain:39521
2008-07-28 09:08:30,847 [WorkerThread(client_handshake_stage,0)] INFO com.tc.objectserver.handshakemanager.ServerClientHandshakeManager - Client connected ClientID[3]
2008-07-28 09:08:30,927 [TCWorkerComm # 3] INFO com.tc.net.protocol.transport.ConnectionHealthCheckerImpl: DSO Server - Connection to [domain:39521] DISCONNECTED. Health Monitoring for this node is now disabled.
2008-07-28 09:08:30,928 [WorkerThread(channel_life_cycle_stage,0)] INFO com.tc.objectserver.handler.ChannelLifeCycleHandler - Received transport disconnect. Shutting down client ClientID[3]
2008-07-28 09:08:30,929 [WorkerThread(channel_life_cycle_stage,0)] INFO com.tc.objectserver.persistence.impl.TransactionStoreImpl - shutdownClient() : Removing txns from DB : 0

What might be the reason for this? Both server and first client use one tc-config.xml to start. The <server> element looks like this:

Code:

 <server host="domain" name="BOX_1" bind="10.152.113.128">
        <dso-port>9510</dso-port>
        <jmx-port>9520</jmx-port>
 </server>

Thanks gkeim! bind attribute has done the trick. One quick question though. As far as I could understand host attribute should always resolve to the IP address that is supplied to bind attribute, is that correct? If it's correct then what happens when host resolves to some other IP address? Perhaps I just not understand what is bind attribute used for...

Ok I've got the following in my tc-config.xml now

Code:

 <servers>
     <server host="10.152.113.128" name="BOX_1">
        <dso-port>9510</dso-port>
        <jmx-port>9520</jmx-port>
     </server>
 
     <update-check>
       <enabled>true</enabled>
     </update-check>
   </servers>

But when I start server it outputs the following:

2008-07-25 09:37:12,878 INFO - JMX Server started. Available at URL[service:jmx:jmxmp://0.0.0.0:9520]
2008-07-25 09:37:13,772 INFO - Terracotta Server has started up as ACTIVE node on 0:0:0:0:0:0:0:0:9510 successfully, and is now ready for work.

Does that mean that config server setting was not loaded

Thanks Chu, but could you possibly tell a little bit more on what exactly do I need to add specifically for clients config? I mean I'll try solution just want to be sure that this is it.

BTW, I thought clients do not parse <server> </server> part of the config. That sounds confusing, if this is not correct then what do you mean by "It'll help them to connect to the TC server"?

I'd like to start Terracotta server and two clients on three different boxes. What do i need to write in server/clients tc-config files in order to make all of them work together?