Hatena::�֥���(Diary)

ablog ���Υڡ����򥢥��ƥʤ��ɲ� RSS�ե����� Twitter

2017-05-22

Amazon Redshift �� PostgreSQL �� VACUUM FULL ��ư���ΰ㤤

Amazon Redshift �� PostgreSQL �� VACUUM FULL ��ư���ϻ��Ƥ��뤬�����㤦���ɤ����������ΰ��������Ѥ��뤬��Redshift �ϡֹԤ��ƥ����ȡפ��������㤦�������Ϥ��⤽�⡢Redshift �� PostgreSQL �Υǡ�����¤���ۤʤ뤿���ǡ�PostgreSQL �ϹԻظ��ǡ����١����Τ��������������ʤΤ��Ф��ơ�Redshift �ϹԻظ��ǥ����Ⱥѥǡ�������Ǽ���Ƥ���*1�������Ȥ����Ƥʤ��ȥ���������Ψ������*2���뤿���Ȼפ����롣

Amazon Redshift �� VACUUM ���ޥ��ɤι�ʸ��ư���ϡ�PostgreSQL �� VACUUM �����Ȥ������˰ۤʤ��ޤ������Ȥ��С�Amazon Redshift �Ǥ��ǥե������ΥХ��塼�������� VACUUM FULL �Ǥ��������ϡ��ǥ������ΰ��������Ѥ������٤ƤιԤ��ƥ����Ȥ��ޤ��� �������Ф��ơ�PostgreSQL ���ǥե������� VACUUM �����ϡ�ñ�����ΰ��������Ѥ����Ƥӻ��ѤǤ����褦�ˤ��������Ǥ���


������


FULL

���ꤵ�줿�ơ��֥� (�ޤ��ϸ��ߤ��ǡ����١����Τ��٤Ƥ��ơ��֥�) �򥽡��Ȥ���ľ���� UPDATE ������� DELETE �����Ǻ����оݤΥޡ������դ����줿�Ԥˤ��ä���ͭ�����Ƥ����ǥ������ΰ��������Ѥ��ޤ��������Х��塼���ϡ����󥿡��꡼���ơ��֥��������ǥå������ƺ������ޤ����� ���󥿡��꡼���ơ��֥��������ǥå������ƺ��������ˤϡ�VACUUM REINDEX ���ץ����������Ѥ��ޤ���

�ǥե������ǡ�VACUUM FULL �ϡ����ʤ��Ȥ� 95 �ѡ������Ȥ������ȺѤߤǤ����ơ��֥��Υ����ȥե������򤹤٤ƥ����åפ��ޤ��� VACUUM �������ȥե������򥹥��åפǤ����С�DELETE ONLY ���¹Ԥ��������ե������ǻĤ��ιԤξ��ʤ��Ȥ� 95 �ѡ������Ȥ������оݤȤ��ƥޡ��������Ƥ��ʤ��ΰ��������Ѥ��ޤ���

�����Ȥ������ͤ�ã���Ƥ��餺 (���Ȥ��� 90 �ѡ������ȤιԤ������Ȥ����Ƥ���) VACUUM �����������Ȥ��¹Ԥ��������ϡ������ʺ������ڥ졼���������¹Ԥ��졢�������줿�ԤΥ��ڡ����� 100 �ѡ������Ȳ��������ޤ���

���Ĥ��ơ��֥����Ф��ƤΤ��ǥե������� VACUUM �������ͤ��ѹ��Ǥ��ޤ��� 1 �Ĥ��ơ��֥����Ф����ǥե������� VACUUM �������ͤ��ѹ������ˤϡ��ơ��֥�̾������ TO threshold PERCENT �ѥ��᡼�����ޤ��ޤ���

VACUUM - Amazon Redshift

�ơ��֥��κ������ˡ����� 1 �İʾ������򥽡��ȥ����Ȥ����������뤳�Ȥ��Ǥ��ޤ����ǡ����������ơ��֥��˺ǽ��˥����ɤ������ȡ��Ԥ��ǥ��������˥����Ƚ��˳�Ǽ�����ޤ��������ȥ������˴ؤ����������������ץ����ʡ����Ϥ��졢�ץ����ʤϤ��ξ��������Ѥ��ơ��ǡ����Υ�������ˡ�����Ѥ����ץ��������ۤ��ޤ���

�����Ȥϡ��ϰϤ����¤��줿�Ҹ�����ΨŪ�˽������뤳�Ȥ��Ǥ��ޤ���Amazon Redshift �ϡ����ǡ����� 1 MB �Υǥ������֥��å��˳�Ǽ���ޤ����ƥ֥��å��κǾ��ͤȺ����ͤ��᥿�ǡ����ΰ����Ȥ��Ƴ�Ǽ�����ޤ����ϰϤ����¤��줿�Ҹ��������������Ѥ������硢�������ץ����å��ϺǾ��ͤȺ����ͤ����Ѥ��ơ��ơ��֥�������������¿���Υ֥��å��򤹤Ф䤯�����åפ��뤳�Ȥ��Ǥ��ޤ���

�����ȥ��������� - Amazon Redshift

(FULL��̵��)�̾���VACUUM��ñ���ΰ����������������������Ѳ�ǽ�ʾ��֤��ѹ����ޤ��� ��¾Ū���å������������Ƥ��ʤ����ᡢ���η��Υ��ޥ��ɤϡ��ơ��֥��ؤ��̾����ɤ߽����������¹Ԥ��Ƽ¹Ԥ��뤳�Ȥ��Ǥ��ޤ��� VACUUM FULL�ϡ��ǥ������֥��å������Ǿ��ˤ��뤿���Υ֥��å����٤륿�ץ��ΰ�ư�ʤɡ��ơ��֥����̾������뤿���ˤ��äȹ��٤ʽ������Ԥʤ��ޤ��� ���ξ��硢���ʤ���®�ˤʤꡢ�ޤ������������ơ��֥����Ф�����¾Ū���å���ɬ�פˤʤ��ޤ���

VACUUM

*1�������ȥ��������ꤷ�Ƥ�������

*2���������ޥåפǥ֥��å��ɹ��򥹥��åפǤ��륱������

2017-05-17

S3�� jQuery ���Ȥä� SSI Ū�ʤ��Ȥ򤹤�

S3 �� Server Side Include ��SSI��Ū�ʤ��Ȥ� jQuery �Ǥ��äƤߤ���Client Side Include�ˡ�


����

  • ���������Х��åȤ� [�ץ��ѥƥ�]-[Static website hosting] ����������
  • [�����ɥݥ�����]�� URL ���֥饦���ǥ����������Ƥߤ���̵������

f:id:yohei-a:20170517142335p:image


����

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PublicReadGetObject",
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:GetObject"
            ],
            "Resource": [
                "arn:aws:s3:::<�Х��å�̾>/*"
            ]
        }
    ]

�ե�����

<html> 
  <head> 
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
    <script> 
    $(function(){
      $("#includedContent").load("ssi.html"); 
    });
    </script> 
  </head> 

  <body> 
     <div id="includedContent"></div>
  </body> 
</html>
<font color="red" size="7">This is ssi content.</font>

����

2017-05-16

���ˤʤ���ʸ3��

sched: Interrupt Aware Scheduler

Linux �Υץ������������塼�������������٤ι⤤CPU�ʳ��˥ץ�����(�����å�)*1�򥹥����塼���󥰤����ѥå��餷����

The patch avoids CPUs which might be considered interrupt-heavy when

trying to schedule threads (on the push side) in the system. Interrupt

Awareness has only been added into the fair scheduling class.

It does so by, using the following algorithm:

--------------------------------------------------------------------------

1) When the interrupt is getting processed, the start and the end times

are noted for the interrupt on a per-cpu basis.

2) On a periodic basis the interrupt load is processed for each run

queue and this is mapped in terms of percentage in a global array. The

interrupt load for a given CPU is also decayed over time, so that the

most recent interrupt load has the biggest contribution in the interrupt

load calculations. This would mean the scheduler will try to avoid CPUs

(if it can) when scheduling threads which have been recently busy with

handling hardware interrupts.

3) Any CPU which lies above the 80th percentile in terms of percentage

interrupt load is considered interrupt-heavy.

4) During idle CPU search from the scheduler perspective this

information is used to skip CPUs if better are available.

5) If none of the CPUs are better in terms of idleness and interrupt

load, then the interrupt-heavy CPU is considered to be the best

available CPU.

---------------------------------------------------------------------------

Linux-Kernel Archive: [PATCH 1/2] sched: Interrupt Aware Scheduler

*1�����Τˤϥ�����

2017-05-13

MySQL �򥽡��������ɤ����ӥ��ɤ���

����

sudo yum install git
sudo yum install cmake
sudo yum install gcc
sudo yum install gcc-c++
sudo yum install ncurses-devel

mysql-build �����󥹥ȡ���

git clone git://github.com/kamipo/mysql-build.git ~/mysql-build
export PATH="$HOME/mysql-build/bin:$PATH"

MySQL ���ӥ�������

mkdir -p ~/opt/mysql
mysql-build -v 5.7.10 ~/opt/mysql/mysql-5.7.10

��ǧ����

  • MySQL����ư����
cd ~/opt/mysql/mysql-5.7.10
./bin/mysqld --initialize-insecure --basedir=.
./bin/mysqld_safe &
  • SQL ���¹Ԥ���
$ ./bin/mysql -u root -e 'SELECT @@version'
+-----------+
| @@version |
+-----------+
| 5.7.10    |
+-----------+

��­

collect2: ld terminated with signal 9 [Killed]

�ȥ��顼���Ф��Τǡ�

Your virtual machine does not have enough memory to perform the linking phase. Linking is typical the most memory intensive part of a build since it's where all the object code comes together and is operated on as a whole.

If you can allocate more RAM to the VM then do that. Alternatively you could increase the amount of swap space. I am not that familiar with VMs but I imagine the virtual hard drive you set-up will have a swap partition. If you can make that bigger or allocate a second swap partition that would help.

Increasing the RAM, if only for the duration of your build, is the easiest thing to do though.

gcc - Why is the linker terminating on me? when i build CLang - Stack Overflow

�򻲹ͤ˥����ꥵ�������礭���ޥ������ӥ�������������������


����

MySQL�Υ����������ɤ����ꤹ��


��­

�ǿ��С��������ʳ��ϰʲ������������������Ǥ��롣


����

Web���󥸥˥��Τ����� �ǡ����١�������[����]���� (Software Design plus)

Web���󥸥˥��Τ����� �ǡ����١�������[����]���� (Software Design plus)

P.168-169

2017-05-12

zsh �� /usr/local/bin �˥ѥ����̤äƤʤ��Ȼפä���

Terminal.app ���� iTerm2 �˾��괹���ơ�zsh �� /usr/local/bin �˥ѥ����̤äƤʤ��Ȼפä��顢�㤦 zsh �Υѥ������ꤷ�Ƥ�����


����