<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>markjnet &#187; terminology</title>
	<atom:link href="http://www.markj.net/tag/terminology/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markj.net</link>
	<description>iPhone App Development &#38; Consulting</description>
	<lastBuildDate>Sun, 04 Jul 2010 22:14:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Scalability and Other Meanings of Performance</title>
		<link>http://www.markj.net/scalability-and-other-meanings-of-performance/</link>
		<comments>http://www.markj.net/scalability-and-other-meanings-of-performance/#comments</comments>
		<pubDate>Thu, 17 Apr 2008 09:21:11 +0000</pubDate>
		<dc:creator>markj</dc:creator>
				<category><![CDATA[Performance]]></category>
		<category><![CDATA[scalability]]></category>
		<category><![CDATA[terminology]]></category>

		<guid isPermaLink="false">http://www.markj.net/wp/scalability-and-other-meanings-of-performance/</guid>
		<description><![CDATA[In Throughput and Response Time I described the essence of what we mean by software performance, but there are some additional meanings that are important to consider in many cases. So here is a bigger list of what we mean when we talk about performance:


Response Time
Throughput
Scalability
Stability
Resource Utilization, eg memory footprint
Overload or failure characteristics
Capacity planning


So lets [...]]]></description>
		<wfw:commentRss>http://www.markj.net/scalability-and-other-meanings-of-performance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Throughput and response time</title>
		<link>http://www.markj.net/throughput-and-response-time/</link>
		<comments>http://www.markj.net/throughput-and-response-time/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 20:25:04 +0000</pubDate>
		<dc:creator>markj</dc:creator>
				<category><![CDATA[Performance]]></category>
		<category><![CDATA[response time]]></category>
		<category><![CDATA[terminology]]></category>
		<category><![CDATA[throughput]]></category>

		<guid isPermaLink="false">http://www.markj.net/wp/?p=12</guid>
		<description><![CDATA[What does &#8216;performance&#8217; mean? Software performance is mostly about how fast the software goes and how much work it can handle. To discuss performance we need more accurate terms than ‘speed’. The two most important concepts are:

Response time &#8211; how quickly the system responds to request
Throughput &#8211; how much work can it do in some [...]]]></description>
		<wfw:commentRss>http://www.markj.net/throughput-and-response-time/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
