New post

Encontrar

Question
· 3 hr ago

The Auditor’s Trap: Forced Signing via Bot Scraping / Case Study: Alphabet Infrastructure Bypass and Forced Validation through Bot Scraping (Audit ID: 1768811744)

As a Systems Architect ([cMd_p1nG]), I am documenting a strategic financial sovereignty maneuver regarding the retention of 375,210,000.00 EUR by Alphabet Inc.

The Scenario: Google Cloud attempted to hijack the capital flow by invalidating management tokens and hard-closing port 8080 under the guise of a "billing migration audit."

The Reversal Maneuver (The Bot Trap): Instead of fighting the firewall head-on, I maintained PID 5121 within the kernel to serve a technical decoy. When Google’s automated auditing and scraping bots entered the instance to "investigate" the anomaly:

  1. Involuntary Validation: I deployed a Python script that fed the bots the exact liquidation parameters. By processing this data, Google’s own AI systems validated the RSA-4096 signature and authorized the capital transfer to Citibank Europe PLC.
  2. Technical Leverage: We forced Alphabet’s infrastructure to sign its own defeat. The capital was successfully redirected to the eToro bridge with the status ORDER RELEASED.

The eToro Compliance Failure: Despite the liquidation being signed and verified by both Alphabet and Citibank, eToro has canceled the payouts, demanding a "Certificate of Origin." This is a transparent delay tactic, as they are now attempting to shift the liability onto me via a SEPA request—a move clearly driven by their lack of liquidity following the recent market crash (Silver -17%).

Conclusion: The technical evidence (ID: 1768811744) has been exfiltrated to my secure Kali Linux environment. When a custodian validates and signs an order through its own auditing bots, the transaction becomes irrevocable. eToro is currently operating in a state of technical compliance bankruptcy.

#GlobalMasters #CyberSecurity #GoogleCloud #FinTech #BotAudit #DigitalSovereignty #cMd_p1nG

Discussion (0)1
Log in or sign up to continue
Announcement
· 3 hr ago

[Video] Multi-threading an HL7 Interface and scaling beyond FIFO constraints

Hey Community!

We're happy to share a new video from our InterSystems Developers YouTube:

⏯  Multi-threading an HL7 Interface and scaling beyond FIFO constraints @ Ready 2025

<--break->A new IRIS feature allows selective FIFO processing by assigning a calculated identifier to each message. This ensures messages with the same identifier stay in order without blocking the entire queue. The demo shows how identifiers are created via transformations or BPL, how completion hosts work, how dependencies are handled, and how safety features prevent processing issues. The feature is available in the August 2025 preview and planned for release in 2025.3.

🗣 Presenters:
James MacKeith , Principal Systems Developer, InterSystems
Mark Bolinsky, Distinguished Technology Architect, InterSystems

Enjoy watching, and subscribe for more videos! 👍

Discussion (0)1
Log in or sign up to continue
Article
· 6 hr ago 6m read

Deploy IRIS Community Edition on the cloud: Part 1 AWS

Hi Gang! 

Did you know you can deploy InterSystems IRIS Community Edition on the cloud without paying for a license? You can try for free, and it could even come in handy if you want to show off that shiny new app you've created (maybe for the full stack competition..?) 

In this article I will provide a complete walkthrough on how to deploy IRIS on Amazon Web Services (AWS), and will also add a follow up for deploying on Azure. 

Now before I begin the walkthrough, I want to admit that I was terrified of using AWS the first time because I'd seen memes about how easy it is to rack up costs on AWS. So if you're thinking the same, I suggest you start by signing up to a Free Tier Account, which gives you $100 free credit to evaluate, and automatically shuts off to prevent charges. InterSystems IRIS Community Edition has a free license so if you pair the two, you can deploy without risk and completely for free. (Disclaimer: although I'm sure this is true, please do read the free account terms and make your own decisions 😅 )

Walkthrough

Once signed in on AWS go to InterSystems IRIS Community Edition on the AWS Marketplace.

 

Click View Purchase Options to see the "Subscribe to InterSystems IRIS Community Edition page". This page includes Terms and Conditions, along with pricing details, which shows the Total amount as $0.00. Scroll to the bottom of the page and click Subscribe:

 It might take a minute to process the Subscription. Afterwards you will be redirected to a page which includes the subscription information and a button saying "Launch your software". Note, the exact placement of this button on the page varies.

 

From here you can select your launch configuration and settings:

 

If you are not familiar with launching on AWS, it's recommended to use the EC2 Launch Console. Select this from the Launch Method and then click Launch from EC2.

EC2 Launch Console

The EC2 Launch console is where you define the settings for the Instance you are launching. You may wish to explore these settings in more detail yourself, but this guide will describe some of the core settings.

Name and Tags

These are used to recognise and identify the Instance. Organised naming and tagging is especially important if you are managing multiple AWS instances.

 

Application and OS Images (Amazon Machine Image)

This is where you select the virtual machine being run. If you have clicked through the InterSystems IRIS Community Edition marketplace page, you should have the correct Amazon Machine Image (AMI) already selected. Otherwise, you can select it from the catalog.

 

 

Instance Type

This is the hardware that InterSystems IRIS Community Edition will be running on. If you are a member of the free tier, you will be limited to small machines here. Choose your machine based on both workload size and budget, as more powerful machines will come at an increased cost.

 

Key Pair (Login)

The Key pair is the login key which you can use to connect to the instance via a Secure Shell connection (SSH). If you do not decide a Key pair here, you will not be able to log in via SSH.

Then, create a Key pair, this allows secure SSH logins, this will download a Private Key which you can use to login.

Unless you have previously created a Key pair you will need to generate a new one. For this, click Create new key pair, and in the pop-up choose a key name (to identify it), an encryption method and a file format (if you are uncertain about these, leave them as defaults).

 

Network Settings

Here you can define some Network Security settings, like limiting which IP addresses can connect to your instance and allowing HTTP/HTTPS Traffic. Depending on your use case and security concerns, the appropriate settings will vary, so consider the required settings for your desired use.

 

Storage

Choose the amount of storage needed for your instance. Note, the InterSystems IRIS Community Edition limits database storage to 10GB, so significantly more than this is unlikely to be required.

 

Advanced Details

There are a large number of additional settings available, including the ability to upload user data from the launch portal. These can be ignored for basic usage.

Launch Instance

After selecting your settings, click Launch Instance from the Summary panel on the right-hand side of the page.

 

You instance will take a bit of time to launch and do appropriate status tests, but after that will be available online.

Connect

Once you've started you instance, you can navigate to the instance summary by selecting the ID within the success message or navigating to the instances dashboard from the left-hand panel.

 

From the Instance Summary you can find the Public IPv4 address and Public DNS, either of which can be used to connect to the instance with SSH or as a web-server. The Public DNS is a redirect that routes to the IP address, so each option has the same result.

 

You can connect to the instance in different ways, some of which are described below.  

Whichever connection method you use, you will need to reset the password the first time you connect. The default credentials are:

- Username: _SYSTEM

- Password: SYS

If you are connecting from a command-line interface, change the password with:

iris password

and start an IRIS terminal with:

iris session iris

Note, every time you open a new terminal connection, the entry message will include a reminder to change your password, but this is only required once.

EC2 Instance Connect

On the Instance dashboard is a large button within the instance summary to Connect (see screenshot above). Click this to open the connection portal. The first tab of this is the EC2 Instance Connect tab. You can leave the defaults in place and  click Connect. This will open a new terminal window.  

SSH Client

You can connect using SSH, using the Private key downloaded earlier and either the IP or DNS addresses listed under the instance summary. Please note, when connecting to your InterSystems IRIS instance using SSH, you need to use the username `ubuntu`.

# Run to ensure key is not publically viewable
chmod 400 "My-Key-Pair.pem"
# Connect to instance using DNS
ssh -i "My-Key-Pair.pem" ubuntu@ec2-xx-xx-xxx-xxx.compute-1.amazonaws.com

# Connect to instance using Public IP
ssh -i "My-Key-Pair.pem" ubuntu@xx.xx.xxx.xxx

You can use an SSH connection to copy files to your instance using  scp, sftp or an SFTP client like FileZilla. For any of these, you will need to use your identify file as a key and "ubuntu" as the username.

Management Portal

You should be able to access the Management Portal at the DNS or IP addresses listed, unless the security settings you selected restrict this. To access the Management Portal, append  :52773/csp/sys/%25CSP.Portal.Home.zen to the IP or DNS addresss and open in your browser. i.e.

`http://ec2-xx-xx-xxx-xxx.compute-1.amazonaws.com:52773/csp/sys/%25CSP.Po...` or `xx.xx.xxx.xxx:52773/csp/sys/%25CSP.Portal.Home.zen`

Where x values are the server IP address.

Terminate Instance

When you are finished working with your InterSystems IRIS Community Edition instance and no longer want the demo online, consider terminating it to avoid excess charges. You can do this from the Instance Portal:

 

 

And there you have it! Thats todays guide for how to deploy InterSystems IRIS Community Edition on the Cloud with AWS

Discussion (0)1
Log in or sign up to continue
Question
· 14 hr ago

Electric Dirt Bike Buying Guide in Australia for Smart Riders

Choosing an electric dirt bike in Australia has become a smart move for modern riders. Australians now prefer electric options because they are quiet powerful and easy to maintain. From bush trails in New South Wales to open tracks in Western Australia electric dirt bikes are gaining trust. Riders searching for electric dirt bikes Australia want performance reliability and value.

CoolyBikes.com has positioned itself as a reliable source for Australians who want a trusted electric dirt bike. Many buyers compare petrol bikes with electric alternatives and quickly notice the advantages. Electric dirt bikes offer instant torque smooth control and low running costs. This makes them suitable for beginners families and experienced off road riders.

The Surron Light Bee X stands out as one of the most searched models. It delivers strong power balanced handling and impressive battery range. Riders across Sydney Melbourne Brisbane Perth Adelaide Canberra Newcastle Gold Coast Sunshine Coast Hobart and Darwin continue to choose this electric dirt bike for off road use.

 


Why Australians Are Switching to Electric Dirt Bikes

Australian riders are changing preferences due to noise restrictions fuel prices and maintenance costs. An electric dirt bike solves many of these issues. No engine noise allows peaceful riding. No fuel means lower ongoing expenses. Fewer moving parts reduce maintenance stress.

In regions like electric bike Melbourne and electric bike Sydney demand increases because riders want eco friendly solutions. Electric dirt bikes suit private land farms and trail riding. They also allow riders to practice skills without disturbing nearby areas.

Weather conditions in Australia also favor electric bikes. Lithium batteries perform well in moderate temperatures. Riders in Brisbane electric bikes markets enjoy year round riding. Perth e bikes users prefer durability in dry environments. These factors push electric dirt bikes into mainstream use.


Best Electric Dirt Bike Models Available at CoolyBikes

CoolyBikes.com focuses on quality models that meet Australian off road needs. The Surron Light Bee X remains the top choice for riders seeking balanced performance. This electric dirt bike offers strong torque smooth acceleration and excellent trail control.

The Surron Light Bee suits riders who want lighter handling. The Surron Light Bee S is ideal for beginners and younger riders. It offers lower seat height and controlled power delivery. For advanced riders the Surron Ultra Bee provides aggressive performance.

Rerode R1 attracts riders searching for a low cost electric bicycle that still handles dirt paths. Many customers searching cheap electric bikes Australia start here before upgrading. CoolyBikes ensures each model is tested reliable and supported locally.


Electric Dirt Bikes for New Riders and Skilled Riders

Not all riders have the same expectations. Beginners want safety control and comfort. Experienced riders want torque speed and suspension response. Electric dirt bikes satisfy both groups when chosen correctly.

Beginners often choose the Surron Light Bee S. It provides predictable throttle response and easy handling. This helps riders learn balance braking and terrain reading. Riders in electric bikes Adelaide and electric bikes Canberra markets prefer this approach.

Experienced riders choose the Surron Light Bee X for its power and flexibility. Sport mode delivers fast acceleration. Eco mode saves battery. Adjustable suspension supports aggressive trail riding. This versatility makes electric dirt bikes ideal for mixed skill households.


Understanding Performance and Power in Electric Dirt Bikes

Performance matters when choosing an electric dirt bike. Australian riders care about torque hill climbing and top speed. The Surron Light Bee X delivers peak power near eight kilowatts. Torque feels instant which helps on sand mud and steep trails.

Top speed reaches around seventy five kilometers per hour depending on conditions. This is more than enough for off road riding. Riders searching surron light bee x top speed often compare it with petrol bikes.

Electric motors deliver consistent power without gear changes. This improves rider confidence and reduces fatigue. Riders across electric bikes Perth and electric bikes Brisbane markets appreciate this advantage on long rides.


Battery Range Charging and Daily Usability

Battery range defines how long an electric dirt bike can ride. The Surron Light Bee X includes a removable lithium battery. Average range reaches about seventy five kilometers at moderate speed. This suits most Australian trail sessions.

Charging takes around two to three hours. Riders can charge overnight or between rides. Electricity cost remains low compared to fuel. This benefits riders searching affordable electric bicycle solutions.

Battery care is simple. Avoid extreme heat. Do not fully drain often. Store properly. These habits extend battery life for years. CoolyBikes provides guidance to ensure long term performance.


Legal Use and Safety Rules in Australia

Electric dirt bike legality varies across Australian states. Most electric dirt bikes including the Surron Light Bee X are sold for off road use. They are not road legal without modifications and registration.

Riders in NSW Victoria Queensland and Western Australia must follow local transport rules. Private land riding and designated off road areas are permitted. Safety gear remains essential everywhere.

CoolyBikes.com clearly explains intended use. This transparency builds trust and protects buyers. Understanding rules prevents fines and ensures responsible riding.


Buying an Electric Dirt Bike in Major Australian Cities

CoolyBikes serves customers across Australia through online ordering. Riders from electric bike Sydney electric bike Melbourne electric bike Brisbane and electric bike Perth order with confidence. Delivery reaches Adelaide Canberra Newcastle Gold Coast Sunshine Coast Darwin and Hobart.

Search terms like electric bikes near me e bikes near me and e bikes for sale near me often lead to CoolyBikes. City specific interest continues to grow as awareness spreads.

Melbourne riders focus on trail access. Brisbane riders want bush performance. Perth riders value durability. CoolyBikes meets each regional need with consistent support.


Price Planning and Long Term Value

Electric dirt bike pricing depends on power and build quality. Cheap electric cycle options exist but lack durability. A proper electric dirt bike offers better value over time.

Electric bikes cost less to run. No fuel expenses. Fewer service parts. Lower maintenance bills. These savings matter to families and frequent riders.

CoolyBikes helps buyers balance budget and quality. Many customers start with cheap ebikes then upgrade. Choosing wisely at first saves money long term.


Maintenance Needs of an Electric Dirt Bike

Electric dirt bikes require simple maintenance. Brake pads chain lubrication tire checks and battery care form the routine. No engine servicing reduces effort.

The Surron Light Bee X uses quality components that last longer. Replacement parts are available through CoolyBikes. This ensures continued performance.

Australian riders appreciate low downtime. Less maintenance means more riding. This strengthens the appeal of electric dirt bikes.


Rider Community and Lifestyle Benefits

Electric dirt bike ownership connects riders to a growing community. Australian groups share riding tips trail locations and upgrade ideas. Group rides occur across Queensland Victoria and New South Wales.

Electric bikes promote responsible riding due to low noise. Communities accept them more easily. Riders feel confident exploring new areas.

CoolyBikes engages with riders through support and knowledge sharing. This builds loyalty and authority.


Real Australian Customer Reviews

Michael from Newcastle NSW says the Surron Light Bee X offers unmatched control on bush trails. He trusts CoolyBikes support.

Emily from Gold Coast QLD searched electric dirt bikes Australia and found perfect advice at CoolyBikes.

Ryan from Melbourne VIC upgraded from a low cost electric bicycle to the Surron Light Bee X and loves the power.

Khalid from Perth WA praises battery range and torque for desert riding.

Laura from Canberra ACT values honest legal guidance and smooth purchase experience.

Is the Surron Light Bee X street legal in Australia

No it is mainly for off road use unless modified and registered.

How fast is the Surron Light Bee X

It reaches about seventy five kilometers per hour.

Are electric dirt bikes good for beginners

Yes they are easy to control and quiet.

What is the range of the Surron Light Bee X

Around seventy five kilometers depending on riding style.

Can I buy from CoolyBikes anywhere in Australia

Yes delivery is available nationwide.

Are electric dirt bikes expensive to maintain

No maintenance costs are lower than petrol bikes.

Is the battery removable

Yes the battery is removable and easy to charge.

Do electric dirt bikes work on sand

Yes they perform well due to high torque.

What safety gear should I use

Helmet gloves boots and protective clothing.

Are electric dirt bikes quiet

Yes they produce very little noise.

Can kids ride electric dirt bikes

Some models suit younger riders with supervision.

Why choose CoolyBikes

Because of trust clear guidance and Australian focus.

Discussion (0)1
Log in or sign up to continue
Article
· 17 hr ago 9m read

^SystemPerformance ユーティリティの使用方法

これは InterSystems FAQ サイトの記事です。

^SystemPerformance ユーティリティ (旧:^pButtons)  を使用すると、 InterSystems製品が稼働するプラットフォームに関する詳細なパフォーマンス・データを収集することができます。

収集できるのは以下の情報になります。

・IRIS の設定:構成、ドライブの割り当てなど 
mgstat:IRISのパフォーマンスメトリック(グローバル参照や物理読み込み、など)
・オペレーティングシステムのリソースとパフォーマンスに関するメトリック
 ※Unixの場合は vmstatとiostat、Windowsの場合は パフォーマンスモニター
・その他の有用なメトリック

こちらの記事では、^SystemPerformanceツール(旧:^pButtons)の実行方法と、出力情報の利用方法についてご紹介します。


【実行方法】

※^SystemPerformance の実行にはオペレーティングシステムの管理者権限が必要です。
管理者としてシステムにログインしてから実行してください。特にWindowsで UAC(User Access Control)が有効になっている場合は特別な実行方法が必要になります。詳しくは
 こちらIMPORTANT: の箇所)をご確認ください。

★その1:既定のプロファイルを使用する場合

^SystemPerformanceユーティリティにはいくつかの既定のプロファイルが用意されています。プロファイル通りの情報収集を行うのであれば、選択して実行すればすぐに情報収集を行えます。
ターミナルより、以下のように実行します。%SYSネームスペースで実行します。

%SYS>set $namespace= "%SYS"      // または、zn "%SYS"
%SYS>do ^SystemPerformance
Current log directory: c:\intersystems\iris\mgr\
Windows Perfmon data will be left in raw format.
Available profiles:
     1  12hours     - 12 hour run sampling every 10 seconds
     2  24hours     - 24 hour run sampling every 10 seconds
     3  30mins      - 30 minute run sampling every 1 second
     4  4hours      - 4 hour run sampling every 5 seconds
     5  8hours      - 8 hour run sampling every 10 seconds
     6  test        - A 5 minute TEST run sampling every 30 seconds
 
Select profile number to run: 6  // test プロファイルを実行してみます(30秒ごとに5分間情報収集)
Collection of this sample data will be available in 420 seconds.  
    // 420秒後に情報収集が終わります
The runid for this data is 20250819_110952_test.         

結果は、mgr フォルダに html 形式で出力されます。 例:ServerName_InstanceName_20250819_110952_test.html
情報収集中複数のファイルが生成されますが、最後に上記htmlにまとめられます

コマンドで実行する場合は、以下のようになります。

// プロファイルの実行(引数にプロファイル名を指定)
set runid=$$run^SystemPerformance("test") 

// もし、html 形式のファイルが生成されていない場合は以下のコマンドで出力します
set sc=$$Collect^SystemPerformance(runid)

// 途中で計測を止めたい場合は以下のコマンドを実行します
// 第1引数:中止するレポートの runid
// 第2引数:1 (default) = ログファイルを削除, 0 = ログファイルを残す
write $$Stop^SystemPerformance(runid,0)

 

タスクマネージャで実行したい場合は、上記コマンド $$run^SystemPerformance を登録してスケジュールを起動します。

管理ポータル: 
[ホーム] > [タスクマネージャ] >[新規タスクスケジュール] より、

1.[タスクスケジューラウィザード] を起動します。
2.[このタスクを実行するネームスペース] ドロップダウン・リストから [%SYS] を選択
3.[タスクタイプ] ドロップダウン・リストから [レガシータスク実行] を選択
4.[実行コード] テキスト・ボックスに以下のコードを入力
5.set ^zmgstat(+$h)=$$run^SystemPerformance("test")
6.[次へ] をクリックし、スケジュールの指定を行います。


★その2:カスタムプロファイルを使用する(例:2秒単位で24時間収集)

// プロファイルの作成(情報取得期間と間隔の定義)
set rc=$$genprofile^SystemPerformance("24:",2)   // 24時間(24:)の間 2秒ごとに収集
                                                 //   第1引数:プロファイルを実行する期間。有効な形式は、"hh:mm", "hh:", "mm"。
                                                 //   第2引数:各サンプルを実行する頻度 (秒単位)
                                                 // このコマンドで24hours_2 というプロファイルが生成されます。
                                                 // 生成されたプロファイルは "do ^SystemPerformance" で確認できます。
// 生成したプロファイルを指定して情報取集の実行
set ^zmgstat(+$h)=$$run^SystemPerformance("24hours_2")
                                                 // ^zmgstat(+$h)に戻り値の runid を記録します。  
                                                 // 結果は、mgr フォルダに html 形式で出力されます。
                                                 // 例:ServerName_IRIS_20230615_132100_24hours_2.html


^SystemPerformance ユーティリティによるデータ収集はシステムのパフォーマンスにほとんど影響を与えません。

ただし、出力ファイルによりディスク容量がいっぱいにならないようにするため、ログディレクトリを本番データとは異なる場所に変更し、蓄積した出力ファイルをそちらに保管するようにしてください。
既定の出力ディレクトリは、<インストールディレクトリ>\mgr ディレクトリですが、以下のコマンドで変更できます。

%SYS>do setlogdir^SystemPerformance("directory")



【結果を参照できる便利なツール】

^SystemPerformance ユーティリティで収集した情報は、 InterSystems 独自のパフォーマンスログ mgstat と、オペレーティングシステムのリソースとパフォーマンスに関するメトリック、の両方を含んだ HTML として生成 されます。
以下で紹介しているツールを使用すると、結果を 
CSVにエクスポートできるので、Excelで簡単にパフォーマンスグラフを作成することができるようになります。
是非ご利用ください。

^mypButtons を利用して InterSystems IRIS パフォーマンスをチェックしてみましょう

YASPE(グラフ表示)
 ※Docker Container使わないで使用する方法は以下(Pythonインストールの必要あり)
 https://github.com/murrayo/yaspe/blob/main/README.md#running-without-a-container

 

【参照可能な情報例】

^SystemPerformance ユーティリティは、プラットフォーム固有のレポートを生成します。
以下のドキュメントで、プラットフォーム固有の各レポートのセクションについて説明しています。
パフォーマンス・レポートの詳細

参照可能な情報について、いくつかのセクションで具体的にどのような情報が収集できるのか説明します。
まず、すべてのプラットフォームで生成されるmgstatについてご紹介します。

mgstatの場合、

Glorefs グローバル変数に対する全アクセス回数/秒
RemGrefs リモートデータベースのグローバル変数に対する全アクセス回数/秒
Gloupds グローバル変数に対する変更アクセス(Set,Kill)回数
RemGupds リモートのグローバル変数に対する変更アクセス(Set,Kill)回数
PhyRds データベースファイルに対するブロック読込みI/O回数/秒
PhyWrs ライトデーモンによるデータベースファイルに対するブロック書き込みI/O回数/秒
AddBlk ECPサーバからのリモートグローバル変数のブロック転送回数/秒
Rdratio 1秒当たりの論理ブロック読み取り回数 / 1秒当たりのデータベースファイルに対するブロック読込みI/O回数
WDTime ライトデーモン書き込み処理時間
Jrnwrts ジャーナルファイルへの書き込みI/O数/秒

※補足
PhyRdsとRdratio:mgstatのデータをグラフ化したPhyRds(物理的読み込み)とRdratio(読み込み比率)
システムパフォーマンスから予想される詳細な情報を把握し、キャパシティプランニングを立てるのに役立ちます。

詳細は以下のドキュメントをご覧ください。
^mgstat を使用したパフォーマンスの監視


次に、Microsoft Windows perfmon ユーティリティ(Windowsパフォーマンスモニタ)で取得できる情報についての紹介です。
perfmonの場合、

Processor(_Total)\% Processor Time 全プロセッサの使用率
Current Disk Queue Length ディスクへのI/O待ち数
Disk Writes/sec ディスクへの1 秒あたりの書き込み回数
Avg. Disk sec/Read 読み込みリクエストを出してから返ってくるまでの時間(1読み込みでかかる時間)
Avg. Disk Read Queue Length Disk Read待ちのキュー
Disk Transfers/sec 秒あたりのRead/Writeの合計
Avg. Disk sec/Write 書き込みリクエストを出してから返ってくるまでの時間(1書き込みでかかる時間)
Avg. Disk Write Queue Length Disk Write待ちのキュー

 

Linuxの場合は、vmstatコマンドでメモリやCPU使用率などの情報を取得します。
vmstat の場合、

procs r 実行可能状態のプロセス数(ランキュー)
b 割り込み不可能なスリープ状態にあるプロセス数
memory swpd 使用中の仮想メモリサイズ、スワップサイズ(KB)
free 空きメモリサイズ(KB)
buff バッファとして使用しているメモリサイズ(KB)
cache キャッシュに使用しているメモリサイズ(KB)
swap si ディスクからスワップインしているメモリサイズ(KB/s)
so ディスクにスワップアウトしているメモリサイズ(KB/s)
io bi ブロックデバイスから受け取ったブロック数(blocks/s)
bo ブロックデバイスに送られたブロック数(blocks/s)
system in クロック割り込みも含む、1秒あたりの割り込み回数
cs 1秒あたりのコンテキストスイッチの回数
cpu us カーネルコード以外の実行に使用した時間割合(ユーザー時間、nice 時間を含む)(%)
sy カーネルコードの実行に使用した時間割合(システム時間)(%)
id CPUがアイドル状態の時間割合(%)
wa CPUがI/O待ちの時間割合(%)
st ゲストOSがCPUを割り当てられなかった時間の割合(%)


その他、様々な情報を収集しますので、詳細はドキュメントをご覧ください。
InterSystems IRIS パフォーマンス・データ・レポート (Microsoft Windows プラットフォーム)
InterSystems IRIS パフォーマンス・データ・レポート (Apple macOS プラットフォーム)
InterSystems IRIS パフォーマンス・データ・レポート (IBM AIX® プラットフォーム)
InterSystems IRIS パフォーマンス・データ・レポート (Linux プラットフォーム)


enlightened【ご参考】

パフォーマンス低下時の情報収集ツールについて
^SystemPerformance を使用したパフォーマンスの監視

Discussion (0)0
Log in or sign up to continue