News & Analysis

Comment


Boab

6/17/2011 2:05 PM EDT

Is this a marketing ploy??? seems like the time stamp is not worth a lot on its ...

More...



Kiran_NSN

5/21/2011 2:35 PM EDT

How is this different from IEE1588 or ToP protocol used in transport layer of ...

More...

cPacket opens up real time network timestamping protocol

Bernard Cole

5/16/2011 10:05 PM EDT

Mountain View, Ca.- cPacket Networks has placed in the public domain a new solution for accurate timestamping of high speed network traffic in real-time that it thinks deals with high performance networking “hiccups.”

According to Rony Kay, founder and CEO of cPacket, with the new protocol microbursts of latency or jitter -- can be identified immediately, and addressed before negatively impacting system performance.

By placing this software solution in the public domain, he said, cPacket is enabling data center operations, high frequency trading platforms, and application developers to benefit from real-time accurate timestamping in high speed networks, at no cost.

“In today’s environment, high speed networks are at the heart of many organizations’ IT infrastructures,” said Kay. “Data centers rely on these networks to deliver services and applications; high performance computing depends on them for scientific applications, complex simulations, medical research, and others; and financial organizations rely on very fast networks for high frequency trading.

“In the latter, a microsecond delay in trades can cause losses of millions of dollars. For such networks, accurate timestamping is a crucial component of network monitoring, to ensure a consistent quality of service, and to address performance problems in a timely manner.”

Historically, software monitoring solutions have had to rely on timestamping by specialized network interface cards (NIC) in conjunction with span ports or aggregation taps. But timestamping at the NIC level, said Kay, creates inherent inaccuracies caused by buffering,
queuing, and random variations of span ports or aggregation before the data arrives at the NIC.

“These fundamental inaccuracies contaminate the upstream software analytics, becoming the root cause of misleading results, and results in less-than-optimal applications performance,” he said. “Monitoring applications with existing solutions is like driving a car on a freeway with a broken speedometer, and then wondering why you are getting speeding tickets.

” In this new approach, the accurate real-time information obtain is timestamped on the applications data on the fly directly “at the wire,” before queuing, buffering, or aggregations can alter its timing behavior.

The company’s new software enables users and application developers to seamlessly integrate such real-time timestamping into existing solutions, or into open source tools like Tcpdump, Wireshark, and n2disk.

When used with hardware timestamping directly at the wire, said Kay, the software enables any application to take full advantage of the most accurate inline timestamping in a standard format (including pcap, libcap, etc.).

The standard format and seamless integration means no changes to the user’s application software are required. cPacket is making this new software and driver available free of charge in the public domain to customers, application developers, other solution vendors, universities and the open source community.

The source code for the software is available now from cPacket at www.cpacket.com/tsutils. All cPacket solutions support this real-time timestamping. To learn more about cPacket go to www.cpacket.com.




Robotics Developer

5/17/2011 9:37 AM EDT

An interesting idea and it is great that they are offering it open source! I wonder how many other things could be done with this that have not been thought of?

Sign in to Reply



chanj

5/17/2011 5:13 PM EDT

It is indeed a very interesting idea. Where can they timestamp the packet? At which layer. Link layer information stays within LAN. IP layer has a timestamp field which doesn't seem to provide what cPacket claims. At application layer will confuse the application unless cPacket modules are widely implemented.

Nonetheless, by providing accurate timestamp doesn't really resolve any latency issue. It will provide information where the hiccups happens. Does it provide better information than ping and traceroute?

Sign in to Reply



LarryM99

5/19/2011 2:19 PM EDT

It could be used to adjust to variance more quickly. If the receiver checks the delta time of transfer for each packet and maintains history then it can detect variance on a per-packet basis. That still doesn't tell it deterministically how long it will take for the next one, but it should be as close as you can realistically get.

Larry M.

Sign in to Reply



Kiran_NSN

5/21/2011 2:35 PM EDT

How is this different from IEE1588 or ToP protocol used in transport layer of mobile back haul networks?

Sign in to Reply



Boab

6/17/2011 2:05 PM EDT

Is this a marketing ploy??? seems like the time stamp is not worth a lot on its own, it would need to be attached to a piece of hardware to gain any benefit from it.

Sign in to Reply



Please sign in to post comment

Navigate to related information

EE Buzz DesignCon

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)