<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Sybase performance in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773823#M942591</link>
    <description>Has the database been tuned? Has the table been indexed? Look at your cache hit ratios. They should be in the high 90s.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Marty</description>
    <pubDate>Fri, 26 Jul 2002 18:09:53 GMT</pubDate>
    <dc:creator>Martin Johnson</dc:creator>
    <dc:date>2002-07-26T18:09:53Z</dc:date>
    <item>
      <title>Sybase performance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773822#M942590</link>
      <description>I have a sybase dataserver process that runs high cpu with a wait state on PRI. Attached is a glance snapshot. Freshly installed 11.00 O/S with current patches applied. The DBA's are trying to a large table. Any clues?</description>
      <pubDate>Fri, 26 Jul 2002 17:47:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773822#M942590</guid>
      <dc:creator>Ken Hubnik_2</dc:creator>
      <dc:date>2002-07-26T17:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: Sybase performance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773823#M942591</link>
      <description>Has the database been tuned? Has the table been indexed? Look at your cache hit ratios. They should be in the high 90s.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Marty</description>
      <pubDate>Fri, 26 Jul 2002 18:09:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773823#M942591</guid>
      <dc:creator>Martin Johnson</dc:creator>
      <dc:date>2002-07-26T18:09:53Z</dc:date>
    </item>
    <item>
      <title>Re: Sybase performance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773824#M942592</link>
      <description>Ken:&lt;BR /&gt;&lt;BR /&gt;It has been a long time since I have dealt with Sybase, but...welcome to Sybase.  There is a reason you configure N-1 dataservers (where N is the number of CPUs).  Each dataserver process will consume a CPU, even when the database is "quiet".  Maybe someone will tell us that this is antiquated knowledge.&lt;BR /&gt;&lt;BR /&gt;-dlt-</description>
      <pubDate>Sat, 27 Jul 2002 00:46:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773824#M942592</guid>
      <dc:creator>David Totsch</dc:creator>
      <dc:date>2002-07-27T00:46:59Z</dc:date>
    </item>
    <item>
      <title>Re: Sybase performance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773825#M942593</link>
      <description>Does the machine run other applikations also? It seems that you have more CPUs availible that you might consider to run Sybase on. The parameter "Online engines" states how many processes it should run. Inside Sybase, sp_sysmon shows how Sybase thinks of its performance.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Johan</description>
      <pubDate>Tue, 30 Jul 2002 10:03:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sybase-performance/m-p/2773825#M942593</guid>
      <dc:creator>Johan Bergwitz</dc:creator>
      <dc:date>2002-07-30T10:03:55Z</dc:date>
    </item>
  </channel>
</rss>

