<!- .... ->
<log4net>
<appender name="RollingLogFileAppenderLogstash" type="log4net.Appender.RollingFileAppender">
<encoding value="utf-8" />
<!--该目录必需有 IIS用户 写权限-->
<file value="X:/var/log/[app_name]/logfile.log" />
<appendToFile value="true" />
<rollingStyle value="Date" />
<lockingModel type="log4net.Appender.FileAppender+MinimalLock" />
## Consumer Throughput: Single consumer thread, no compression | |
## Consumer Throughput: 3 consumer thread, no compression | |
bin/kafka-consumer-perf-test.sh --topic benchmark-3-3-none \ | |
--zookeeper kafka-zk-1:2181,kafka-zk-2:2181,kafka-zk-3:2181 \ | |
--messages 15000000 \ | |
--threads 1 |
Producer | |
Setup | |
bin/kafka-topics.sh --zookeeper esv4-hcl197.grid.linkedin.com:2181 --create --topic test-rep-one --partitions 6 --replication-factor 1 | |
bin/kafka-topics.sh --zookeeper esv4-hcl197.grid.linkedin.com:2181 --create --topic test --partitions 6 --replication-factor 3 | |
Single thread, no replication | |
bin/kafka-run-class.sh org.apache.kafka.clients.tools.ProducerPerformance test7 50000000 100 -1 acks=1 bootstrap.servers=esv4-hcl198.grid.linkedin.com:9092 buffer.memory=67108864 batch.size=8196 |
If you are adventurous, here the process to have Hipchat working in your favourite IRC client:
-
First, you need to install the IRSSI XMPP plugin. You can find this package in your distribution, but I advice you to use the latest version possible if you don't want this segfault errors everywhere: http://gna.org/bugs/?20487
-
The first version released after the patch fix is the 0.52-2 that you can download here: https://launchpad.net/ubuntu/+archive/primary/+files/irssi-plugin-xmpp_0.52-2_amd64.deb (No dependencies so it should work in any Debian distributions)
-
Once it's done. You have to configure IRSSI. Either via command line, either manually in the ~/.irssi/config file. I followed this thread: http://cybione.org/lists/irssi-xmpp-list/msg00339.html and it was pretty successful.
-
You can find your XMPP access on your HipChat account on this page: https://boxuk.hipchat.com/account/xmpp. Everything has a XMPP account id. Even the Rooms name. So you have to use these instead of the real names for your I
param | |
( | |
[string] $EnvironmentName, | |
[string] $Version, | |
[string] $ProjectName, | |
[string] $OctopusApiKey, | |
[string] $OctopusServerUrl, | |
[string] $ReleaseNotes | |
) |
if ($OctopusEnvironmentName -eq "Production") { | |
# in production, we need to | |
#Create a URI instance since the HttpWebRequest.Create Method will escape the URL by default. | |
$URL = "http://api.newrelic.com/deployments.xml" | |
$post = "deployment[account_id]=<id here>&deployment[user]=OctopusDeploy&deployment[app_id]=<app id here>&deployment[revision]=($OctopusPackageVersion)" | |
$URI = New-Object System.Uri($URL,$true) | |
#Create a request object using the URI | |
$request = [System.Net.HttpWebRequest]::Create($URI) | |
"And have a healthy disregard for rules. There are way too many rules, and they usually have only | |
one effect: to slow down those who are active. If you believe your activities are in the best | |
interest of the company that employs you - yet you fear you have broken enough rules that you | |
might be fired - then you are doing well." | |
--Sebastian Thrun | |
http://www.reddit.com/r/IAmA/comments/v59z3/iam_sebastian_thrun_stanford_professor_google_x/c51gi53 |
# | |
# Assumptions | |
# | |
# 1. If you have a Octopus release deployed, say 1.0.0.73, there is a git | |
# tag set for that commit in GitHub that is "v1.0.0.73". | |
# | |
# 2. You have TeamCity label each successful build in GitHub with the format | |
# "v{build number}. Sidenote: it appears that TeamCity only labels the | |
# default branch, but not feature branches. | |
# |
Set-Alias MSBuild (Join-Path -Path (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0").MSBuildToolsPath -ChildPath "MSBuild.exe") | |
Set-Alias MSBuild (Join-Path -Path (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\3.5").MSBuildToolsPath -ChildPath "MSBuild.exe") | |
Set-Alias MSBuild (Join-Path -Path (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0").MSBuildToolsPath -ChildPath "MSBuild.exe") |