忍者ブログ

EA備忘録っぽい

有料EA、自作EAを使用したFX取引について日々の感想や記録。 忘れっぽいので、備忘録も兼ねて。 twitter https://twitter.com/reon0079

[PR]
×

[PR]上記の広告は3ヶ月以上新規記事投稿のないブログに表示されています。新しい記事を書く事で広告が消えます。

WIN-VPS CPUについて
VPS変更から2週間が経ちましたが、未だWIN-VPS(ブロンズ3)が安定しません。

①CPU稼働率が常に100%近くで動きが悪い
②Windows Server2016 使用でメール送信が出来ない

①についてABLENET(WIN2プラン)と比較(確認)しました。

WIN-VPS


ABLENET


私の認識不足でありましたが、WIN-VPSのCPUパワーは2GHz、これは2GHzのCPUを1個使用という意味だったようです。

対してABLENETは3コアとあり、実際に3つのプロセッサが稼働しているようです。

WIN-VPS


ABLENET


ちなみに自PC 4コア8プロセッサの場合


安さとメモリ、NYのデータセンターに目が行ってしまい、契約してしまいましたが、冷静にシルバープランとの違いを確認すれば、事前に分かったかもしれません。

WIN-VPS シルバー


今までのように3コアもしくはスペックアップして4コア並みのCPUパワーを求めるのであれば、シルバープラン2or3にすべきかなぁと。
メモリはそんなにいらないんですが…

まあ、1年契約してしまったので、今更使わないわけにもいかず、使い道を再検討する必要がありそうです。

当面は海外ブローカーでNYが有利なTitan、XMのスキャルピング系EAに限って、WIN-VPSを使用。
それ以外(TitanだけどグルトレとかCPU負荷の多そうなもの)はABLENETへ再度引越し。
ABLENETは負荷が多そうなら、オプションで仮想CPU、メモリを追加しようと思います。

②SMTPサーバーに接続できませんエラーが出てメールが使えません
MT4からのメールテストがNG、試しにOperaメールを入れてみても同様。
自PCやABLENETでのテストはもちろん問題なし。

これついてはVPSの問題ではなく、私の知識不足だと思われ、未だ格闘中。
いい加減面倒なので、諦めムードです。
私にはWindowsServer2008R2が合っているようです(^-^;

拍手

PR

コメント

1. 無題

You maʏ play it anytime you want.? Daddy answered.
?As a result of talking about how greɑt God is makes
him blissful and its worship. Play it Ьefore y᧐u fall asleeр tonight and once үoս
wake uр within the morning and God can be close
to you all day long.

2. 無題

Thanks for sharing your thoughts about EA備忘録っぽい.

Regards

3. 無題

Thanks for finally talking about >WIN-VPS CPUについて|VPS|EA備忘録っぽい <Liked it!

4. 無題

Thank y᧐u a lot for sharing tһis with all folks you rеally recognise what yⲟu'гe speaking
ab᧐ut! Bookmarked. Ꮲlease also consult witһ
my site =). Ꮃe can havе a hyperlink tгade contract ƅetween սѕ!

5. 無題

Just desire to ѕay your article is аs astonishing.
Тhe clarity іn your post is just excellent and і can assume you аre аn expert ᧐n this subject.
Fine wіth your permission let me to grab your RSS feed tо keep up to datе with forthcoming post.

Thɑnks a mіllion and pⅼease continue thе rewarding worқ.

6. 無題

Τhanks for sharing y᧐ur thoughts on EA備忘録っぽい.
Ɍegards

7. 無題

Every business will need to have an e-mail page. Websites ranging in dimensions and class coming from a local restaurant to your Fortune 500 company,
have contact pages. Inside my current startup Possess seen a number of requests… through
the pizza delivery guy letting us know he was in front door to potential
investors looking to chat with the management team.



If you're setting the contact page (and getting
the traffic volume of an local restaurant) you might not be
thinking about how to handle your contact requests when traffic increases.
And you should.

Consider putting together automation that alerts support, sales or some
other stakeholders as part of your company when a communication request comes through.

You could make a dropdown field in a form for different types of contact requests.
It is possible to put in place logic in many marketing
automation platforms that sends email alerts to the proper resource
in your startup dependant on what sort of request the viewer selects.



I became buried with contact requests even as launched beta.
Becoming a cloud-based product I saw many product support
requests. So that we mapped form submissions on our
contact page to produce support tickets in Zendesk.


You should also arrange redundancies so contact requests
(important ones!) don't get lost in one particular recipient's inbox.
You can alert multiple recipients, create reminder emails, or
trigger automatic replies to contact requests with information that may solve
their problem. This is actually very easy to arrange with
all-in-one marketing platforms like HubSpot.

8. 無題

All businesses needs to have an e-mail page. Websites ranging in proportion and
class from the local restaurant to some Fortune 500 company, have
contact pages. Within current startup Possess seen many requests… from your pizza delivery guy letting us know he was at the cab end door to potential investors looking to talk with the management team.



If you find yourself setting increase contact page (and receiving the traffic volume
on the local restaurant) you might not want to think about how to regulate
your contact requests when site traffic increases. Nevertheless, you should.


Think of establishing automation that alerts support, sales or another stakeholders
in your company when an e-mail request comes through.
You may create a dropdown field in a form for varieties of contact requests.

You can build logic generally in most marketing automation platforms that sends
email alerts to the appropriate resource within your startup dependant on the kind of request the viewer selects.


I used to be buried with contact requests even as launched beta.
Being a cloud-based product I saw many product support requests.
And then we mapped form submissions on our contact page to
develop support tickets in Zendesk.

You should also setup redundancies so contact requests (important ones!) don't
explore a particular recipient's inbox. You may alert multiple recipients,
create reminder emails, or trigger automatic replies to
get hold of requests with information that could solve their
problem. This 's all a piece of cake to build with all-in-one
marketing platforms like HubSpot.

9. 無題

Hello, i think that i saw you visited my website thus i came to “return the favor”.I am attempting to find things to improve my
site!I suppose its ok to use some of your ideas!!

10. 無題

Olá ! Isso é meio off-topic, mas preciso de alguns conselhos de um blog estabelecido.
É muito difícil para definir o seu próprio blog? Eu não sou
muito técnico, mas pode resolver as coisas muito rápido .

Estou pensando em criação meu próprio, mas eu não
sei onde começar. Tem algum pontos ou sugestões?
Com agradecimentos

11. 無題

I’m not that much of a online reader to be honest but your
sites really nice, keep it up! I'll go ahead and bookmark your
site to come back later. Cheers

12. 無題

Aw, this was an exceptionally good post. Taking a few minutes and actual effort to make a really
good article… but what can I say… I procrastinate a lot and don't seem to get anything done.
コメントを書く