• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Castro AAC

Today I have been doing some heave http test load against the AAC

This is the log file of the http load http://pastebin.com/SzRfnNv6 (I think only the last one of 1137 hits is the good big one)
This was done on my simple win server (i5 3.4 and 8gb RAM) and the page was a character profile (its heavy cuz of signatures and multiple querys). As you can see:

1137 http hits on 59 seconds with a response time of 0.01 seconds and the longest hit duration was 0.08 seconds.

Im running a cache system on the signature of the characters so that helps the load A LOT. During these 1137 http calls the cloaka.exe was using 1.2% CPU and 7.6MB Memory
I will soon bring more load tests

Also some visual updates... I finished the paypal transactions logs

TtFaRHugz.png
 
Nice :). You use this menu? xD:
Custom-Bootstrap-Vertical-Sidebar-Menu.png

---------------------------------------------
 
A skins for your aac to be built ? I have an idea would have been nice as you ive loaded selection of skins
like a this:
SelectThemeTab.png
 
Currently I have 1 default template and anotehr one based off tibia.com website
also making templates the AAC is pretty easy you just need to change a config variable to your template path and thats it.

About your idea... seems cool but I dont really know how to make good looking templates so... kinda hard :(
 
ok good luck certainly test your aac and share my impressions
 
I don't really remember if I already posted this, but this is awesome.
 
So the currently system for getting access to lua returned fields was kinda meh... so I moved to a much more simple one for users

Code:
local data = {}
data["heyy"] = "aaa"
data["magic"] = 32
data["player"] = {}
data["player"]["level"] = 100
return amigo

Using this in a .lua script will give you access to this on a .html template

HTML:
<div class="panel-body">
        The magic number is [[ index .Lua "magic" ]]
        The player level is [[ index .Lua "player" "level" ]]
</div>

I think its a better and easier way
 
Wow. Awesome thread, nice work. Happy to see new projects :)
 
For the first time in years, this thread made me think that the OT community isn't all dead yet.
It have been a long time since I saw a thread with a guy bringing something completely new into the community!

FUCKING GREAT WORK! Keep it up! seriously I wish more people were like you!!!!!!!!
 
<3 I guess I will finish this project soon. Maybe 1 week or 2 left
---
Im currently experimenting some memory leaks on the LUA bindings :( so house auctions and guild wars will need to wait
 
Well the memory leak was fixed :3 and the LUA bindings are now a little bit faster:

1179 request to a custom lua script in 59.38s 0.01 response time. even tho the data transfer was small (6mb) and the lua script wasnt massive either

Code:
local character_module = require("character")
local errorx, deaths = character_module.getCharacterDeaths("Kassem G")
if(errorx ~= true) then
    return false
end
local template = {}
template["list"] = {}
template["list"]["deaths"] = deaths
return template
 
Well the memory leak was fixed :3 and the LUA bindings are now a little bit faster:

1179 request to a custom lua script in 59.38s 0.01 response time. even tho the data transfer was small (6mb) and the lua script wasnt massive either

Code:
local character_module = require("character")
local errorx, deaths = character_module.getCharacterDeaths("Kassem G")
if(errorx ~= true) then
    return false
end
local template = {}
template["list"] = {}
template["list"]["deaths"] = deaths
return template

Tip, have some sort of overload protection..
Imagine a massive DDos or just the event of many players viewing it at same time (DDos would be most likely in this case), so that the system shut itself down to save the computer from heating up.
Sure you might have a DDos protection if you use this website for a server on a dedicated server, but what if the first wave gets through the blocks before it's activated, and the website crashes because overload :p

Something to think about :p

If it was me, I'd have some sort of query/request counter for every minute, once a certain limit is reached, the website will call die("Sorry, system is currently overloaded, please try again in a minute!"); somewhere before all the codes start, making the website a lot more lightweight and wont use as much performance as if it was actually loading all the scripts.
 
This AAC can handle A LOT of traffic (its go :p)

in fact 1179 request in 50seconds is pretty fast

Even tho your idea seems good i will think about the benefits of closing the webserver if it gets like 10k request oer second or so
 
Back
Top