• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
The survival strategy of the cloud computing era 2011 1119 zem_distribution
 

The survival strategy of the cloud computing era 2011 1119 zem_distribution

on

  • 3,224 views

クラウド・コンピューティング時代の 生存戦略 ~ ホスティング・サービスがこの先生きのこるには ~ #osc11tk

クラウド・コンピューティング時代の 生存戦略 ~ ホスティング・サービスがこの先生きのこるには ~ #osc11tk
1.クラウドコンピューティング
2. ホスティングサービスとは何だったのか
3. 次世代ホスティング。この先生きのこるために。

Statistics

Views

Total Views
3,224
Views on SlideShare
2,708
Embed Views
516

Actions

Likes
3
Downloads
33
Comments
0

6 Embeds 516

http://pocketstudio.jp 500
http://webcache.googleusercontent.com 7
http://a0.twimg.com 3
http://paper.li 3
http://matrix.senecac.on.ca 2
https://www.chatwork.com 1

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    The survival strategy of the cloud computing era 2011 1119 zem_distribution The survival strategy of the cloud computing era 2011 1119 zem_distribution Presentation Transcript

    • CloudComputing Hosting Service
    • • –• –• – –
    • • –• –• – –
    • • クラウドは人生(キリッ – • • • – • • – •
    • • – • – • – • – • – • – • • •
    • • –
    • Cloud
    • • – –•
    • • May 1964 “ Barring unforeseen obstacles, an on-line interactive computer service, provided commercially by an information utility, may be as commonplace by 2000 AD as telephone service i today.” l h i is d ”The Computers of Tomorrow by Martin Greenbergerhttp://www.theatlantic.com/past/docs/unbound/flashbks/computer/greenbf.htm
    • Google先⽣⽈く、G l 先⽣⽈く
    • 何かが違う…(;^ω^)何かが違う ( ^ ^)
    • • – –• –
    • • – –• –
    • • – –• –
    • • –• – –
    • • – –• – – – –
    • • –• –• –• –• –
    • • –• –• –• –• –
    • •••••
    • • –• –• –
    • • –• –• –
    • • –• –• –
    • •• – –• – –•
    • ガートナー | プレス・リリース | ガートナー、「先進テクノロジのハイプ・サイクル:2008年」を発表http://www.gartner.co.jp/press/html/pr20080827‐01.html より引用
    • ガートナー | プレス・リリース | ガートナー、「先進テクノロジのハイプ・サイクル:2011年」を発表 市場を変革する可能性のあるテクノロジの成熟度を分析http://www.gartner.co.jp/press/html/pr20110907‐01.html より引用
    • • –• – –• – – –
    • • –• – –• – – –
    • •••• –
    • • •• •• •• •• •• •• •
    • • •• •• •• ••••• ••
    • 78.0% 78.2% 75.3% 72.6% 73.0% 70.8% 66.0% 64.3% 57.8% 46.3% 37.1% 21.4% 13.4%9.2%
    • 78.0% 78.2% 75.3% 72.6% 73.0% 70.8% 66.0% 64.3% 57.8% 46.3% 37.1% 21.4% 13.4%9.2%
    • • – –• – • • • • •
    • • – –• – • • – • •
    • • – –• – –
    • • – –• – –
    • • –•
    • ••
    • ••
    • • –• –• –
    • IaaS• ••• ••• •• •• •
    • •••
    • • – –• – –• –• –
    • • – –• – – –
    • • – – –• – –
    • • – –• – –• – –
    • • ‐ 会員数10万人(2011年9) ‐ サイザックス株式会社 http://zzyzx.co.jp/
    • • ‐ 会員数10万人(2011年9) ‐ サイザックス株式会社 http://zzyzx.co.jp/
    • • ‐ 会員数10万人(2011年9) ‐ サイザックス株式会社 http://zzyzx.co.jp/
    • Throughput 463 287 463.287 MB/sec 1 clients 1 procs max_latency=3.968 max latency=3 968 msThroughput 789.003 MB/sec 2 clients 2 procs max_latency=4.765 msThroughput 1304.08 MB/sec 4 clients 4 procs max_latency=5.390 msThroughput 1939 43 1939.43 MB/sec 8 clients 8 procs max_latency=4.479 max latency=4 479 msThroughput 2534.71 MB/sec 16 clients 16 procs max_latency=12.107 msThroughput 2541.42 MB/sec 32 clients 32 procs max_latency=10.461 msThroughput 1877.46 MB/sec 64 clients 64 procs max_latency 16.700 max latency=16.700 msThroughput 1716.98 MB/sec 128 clients 128 procs max_latency=278.057 msThroughput 1727.13 MB/sec 256 clients 256 procs max_latency=301.766 ms g pThroughput 1517.07 MB/sec 512 clients 512 / p procs max_latency=376.031 ms yThroughput 1252.7 MB/sec 1024 clients 1024 procs max_latency=907.610 msThroughput 722.169 MB/sec 2048 clients 2048 procs max_latency=14085.365 msThroughput 730.51 MB/sec 4096 clients 4096 procs max_latency=26752.568 ms
    • [3] open /fioa/tmp//clients/client4592 failed for handle 16385 (No such file or directory)Throughput /fioa/tmp//clients/client6026 failed for handle 16385 (No such file latency=3 968 ms [3] open /fioa/tmp//clients/client6026 failed for handle 16385 (No such file or directory) [3] open 463 287 MB/sec 463.287 1 clients 1 procs max or directory) max_latency=3.968 [3] open /fioa/tmp//clients/client6482 failed for handle 16385 (No such file or directory)Throughput 789.003 MB/sec 2 clients 2 procs max_latency=4.765 ms [3] open /fioa/tmp//clients/client5040 failed for handle 16385 (No such file or directory)Throughput 1304.08 MB/sec 4 clients 4 procs max_latency=5.390 ms [3] open /fioa/tmp//clients/client6965 failed for handle 16385 (No such file or directory)Throughput /fi /t 43 li t / li t5044 f clients dl 16385 (N [3] open /fioa/tmp//clients/client5044 failed for handle 16385 (No such file or directory) 479 ms [3] 1939 // MB/sec 1939.43 8 il d f h 8 procs max latency=4 max_latency=4.479 h fil di t )Throughput 2534.71 MB/sec 16 clients 16 procs max_latency=12.107 ms [3] open /fioa/tmp//clients/client6055 failed for handle 16385 (No such file or directory)Throughput 2541.42 MB/sec 32 clients 32 procs max_latency=10.461 ms [3] open /fioa/tmp//clients/client4909 failed for handle 16385 (No such file or directory) p pThroughput 1877.46 MB/sec 64 clients ( max_latency y) [3] open /fioa/tmp//clients/client6713 failed for handle 16385 (No such file or directory) 64 procs max latency=16.700 ms 16.700 [3] open /fioa/tmp//clients/client5014 failed for handle 16385 (No such file or directory)Throughput 1716.98 MB/sec 128 clients 128 procs max_latency=278.057 ms [3] open /fioa/tmp//clients/client4971 failed for handle 16385 (No such file or directory)Throughput 1727.13 MB/sec 256 clients 256 procs max_latency=301.766 ms [3] open /fioa/tmp//clients/client6221 failed for handle 16385 (No such file or directory)Throughput /fioa/tmp//clients/client5207 failed for handle 16385 (No such file latency=376.031 ms [3] open 1517.07 MB/sec g p / 512 clients 512 procs max_ or directory) p y [3] open /fioa/tmp//clients/client5207 failed for handle 16385 (No such file or directory)Throughput 1252.7 MB/sec 1024 clients 1024 procs max_latency=907.610 ms [3] open /fioa/tmp//clients/client4139 failed for handle 16385 (No such file or directory)Throughput 722.169 MB/sec 2048 clients 2048 procs max_latency=14085.365 msThroughput 730.51 MB/sec 4096 clients 4096 procs max_latency=26752.568 ms # uptime p 19:24:07 up 7 days,  5:46,  2 users,  load average: 1543.52, 5862.79, 7304.55
    • [3] open /fioa/tmp//clients/client4592 failed for handle 16385 (No such file or directory)Throughput /fioa/tmp//clients/client6026 failed for handle 16385 (No such file latency=3 968 ms [3] open /fioa/tmp//clients/client6026 failed for handle 16385 (No such file or directory) [3] open 463 287 MB/sec 463.287 1 clients 1 procs max or directory) max_latency=3.968 [3] open /fioa/tmp//clients/client6482 failed for handle 16385 (No such file or directory)Throughput 789.003 MB/sec 2 clients 2 procs max_latency=4.765 ms [3] open /fioa/tmp//clients/client5040 failed for handle 16385 (No such file or directory)Throughput 1304.08 MB/sec 4 clients 4 procs max_latency=5.390 ms [3] open /fioa/tmp//clients/client6965 failed for handle 16385 (No such file or directory)Throughput /fi /t 43 li t / li t5044 f clients dl 16385 (N [3] open /fioa/tmp//clients/client5044 failed for handle 16385 (No such file or directory) 479 ms [3] 1939 // MB/sec 1939.43 8 il d f h 8 procs max latency=4 max_latency=4.479 h fil di t )Throughput 2534.71 MB/sec 16 clients 16 procs max_latency=12.107 ms [3] open /fioa/tmp//clients/client6055 failed for handle 16385 (No such file or directory)Throughput 2541.42 MB/sec 32 clients 32 procs max_latency=10.461 ms [3] open /fioa/tmp//clients/client4909 failed for handle 16385 (No such file or directory) p pThroughput 1877.46 MB/sec 64 clients ( max_latency y) [3] open /fioa/tmp//clients/client6713 failed for handle 16385 (No such file or directory) 64 procs max latency=16.700 ms 16.700 [3] open /fioa/tmp//clients/client5014 failed for handle 16385 (No such file or directory)Throughput 1716.98 MB/sec 128 clients 128 procs max_latency=278.057 ms [3] open /fioa/tmp//clients/client4971 failed for handle 16385 (No such file or directory)Throughput 1727.13 MB/sec 256 clients 256 procs max_latency=301.766 ms [3] open /fioa/tmp//clients/client6221 failed for handle 16385 (No such file or directory)Throughput /fioa/tmp//clients/client5207 failed for handle 16385 (No such file latency=376.031 ms [3] open 1517.07 MB/sec g p / 512 clients 512 procs max_ or directory) p y [3] open /fioa/tmp//clients/client5207 failed for handle 16385 (No such file or directory)Throughput 1252.7 MB/sec 1024 clients 1024 procs max_latency=907.610 ms [3] open /fioa/tmp//clients/client4139 failed for handle 16385 (No such file or directory)Throughput 722.169 MB/sec 2048 clients 2048 procs max_latency=14085.365 msThroughput 730.51 MB/sec 4096 clients 4096 procs max_latency=26752.568 ms # uptime p 19:24:07 up 7 days,  5:46,  2 users,  load average: 1543.52, 5862.79, 7304.55
    • • – – –• – – –• –• –
    • •••••
    • ••••
    • • – – –• –• – –• –
    • • – –• – • – • –• – –
    • • 2010 11 2010.11 2011 03 2011.03 09 11 12 09                  11           12 ?2010 2011 2012 Service Released Log Storage (KVS) Analytics L St (KVS) HDD Master Store ( Hadoop relation? ) Image Sto rage (KVS)  Image Sto`rage (KVS) Next Generation  Okuyama Memory Cache Function (KVS) Monitoring System ( RTIME ) ( RTIME )
    • ••
    • • –• – –• – –
    • • –• –• –
    • • –• –• –
    • •• – • • •• –•
    • • – – – • • •
    • • – • – – – • ••
    • • –• –•
    • •••
    • ••••
    • •• – – • • •
    • •••••••••