Optimalisasi Waktu Muat Halaman Web Kuisioner Evaluasi Kinerja Di Jurusan Teknologi Informasi

Raharjo, Novianto Hadi (2022) Optimalisasi Waktu Muat Halaman Web Kuisioner Evaluasi Kinerja Di Jurusan Teknologi Informasi. Undergraduate thesis, Politeknik Negeri Jember.

	Text (Abstract) 1. E41212429 Novianto Hadi Raharjo - Abstract.pdf - Submitted Version Available under License Creative Commons Attribution Share Alike. Download (114kB)
	Text (Bab 1 Pendahuluan) 2. E41212429 Novianto Hadi Raharjo - Bab 1.pdf - Submitted Version Available under License Creative Commons Attribution Share Alike. Download (19kB)
	Text (Laporan Lengkap) 3. E41212429 Novianto Hadi Raharjo - Full Text.pdf Restricted to Registered users only Download (2MB) | Request a copy
	Text (Daftar Pustaka) 4. E41212429 Novianto Hadi Raharjo - Daftar Pustaka.pdf - Submitted Version Available under License Creative Commons Attribution Share Alike. Download (124kB)

Abstract

The Information Technology Department uses a performance evaluation questionnaire website to evaluate lecturer with students as respondent. Evaluation of lecturer performance is carried out at the end of the semester, so that the process of teaching evaluation and learning activities becomes balanced. Lecturers assess students and students fill out lecturer performance evaluation questionnaires. However, the performance evaluation questionnaire website has a drawback, namely the page load time is very long, reaching 3,225 seconds to presenting the evaluation report. This is caused by the number of records, rows of data, in the database storage. The number of records will increase along with the number of evaluations that carried out. Therefore, researchers used the redis, in-memory database tool, to optimize the page load time for presenting the evaluation report. Redis processes data and stores it in server’s memory. So that the web questionnaire will immediately retrieve data from Redis when there is a request to display an evaluation report. The analysis was carried out in two stages with different number of data rows. The first stage uses 267,525 data and the second stage uses 510,000 data. Redis managed to save 1,758 seconds in the first stage and 3,210 seconds in the second.

Actions (login required)

View Item